text: Title: OpenAI API Compatible Endpoints for each Agent (with optional additional arguements)
  Body: ### Feature/Improvement Description
  
  So much new dev now is using OpenAI API compatibility.  Every time there's a new demo CoLab Notebook for a paper, it simply wants an OpenAI Key and can usually accept an OPEN_AI_BASE or openai.api_base endpoint.  
  
  AGiXT's backend really shines as a "one-ring-to-rule-them-all" solution - there's already support for so many diverse providers and the ability to set each agent to use a different provider and with different prompts and settings.  And it's already set up to be a FastAPI server.  
  
  A way to point that Notebook/Langchain/Code at an endpoint for a particular agent in AGiXT (localhost:7437/api/agent/{agent_name}/v1 would be a game-changer.  It would allow use of the same server or docker-image for a half-dozen LLMs, some proxied like revChatGPT (with different model settings, prompts etc), and some local specialized LLMs (ie Gorilla), all handled by one server, ideally with parallel workers for each agent.
  
  That way when the next camel, tree-of-thoughts, fun-new-langchain-experiment comes along, I can simply point it at different agents on a single AGiXT server, each with its own endpoint.
  
  Today's post from the FastChat folks summarizes the point here nicely:
  https://lmsys.org/blog/2023-06-09-api-server/
  
  ### Proposed Solution
  
  Update [app.py](https://github.com/Josh-XT/AGiXT/blob/main/agixt/app.py) to include [OpenAI API Endpoints.](https://platform.openai.com/docs/models/model-endpoint-compatibility)
  
  Specifically /v1/chat/completions, /v1/completions, /v1/embeddings endpoints to each agent.
  
  For example, currently an agent can be reached at /api/agent/{agent_name}/chat
  
  Add 
  /api/agent/{agent_name}/v1/chat/completions
  /api/agent/{agent_name}/v1/completions
  /api/agent/{agent_name}/v1/embeddings
  
  And check that the JSONs/payloads returned are in line with what's spec-ed out at https://platform.openai.com/docs/api-reference
  
  This has been done for individual engines and proxies, for example:
  https://github.com/lm-sys/FastChat/blob/main/docs/openai_api.md
  https://github.com/acheong08/ChatGPT-to-API
  https://github.com/oobabooga/text-generation-webui/tree/main/extensions/openai
  
  ### Acknowledgements
  
  - [X] I have searched the existing issues to make sure this feature has not been requested yet.
  - [X] I have provided enough information for everyone to understand why this feature request is needed in AGiXT.