> For the complete documentation index, see [llms.txt](https://docs.sevenfactor.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sevenfactor.app/iii.-many-llms-one-intelligence.md). # III. Many LLMs, One Intelligence Due to the first principle of modularity of the Seven-Factor App, an enterprise generative AI application should not rely on one single provider, model or version of a Large Language Model (LLM). There are several reasons for this but the three most common ones include 1. The evolution for fast LLM model iterations. 2. Pricing. 3. Requirements of certain agents and information to reside locally in a VPC or in a geo. 4. The requirement to fine-tune smaller models for highly specific tasks. The ensemble of LLMs can be spread across multiple agents or similar to the information layer be discoverable, fine tuned and then deployed using technologies similar to AWS's Bedrock, Azure AI Studio, Nvidia's Inference Microservices (NIMs) platform or Google's Vertex AI. A Seven-Factor App may include either a specialized agent, graph or an LLM router to dynamically route queries and requests to other agents or LLMs. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sevenfactor.app/iii.-many-llms-one-intelligence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.