> ## Documentation Index > Fetch the complete documentation index at: https://docs.promptguard.co/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Every LLM provider the PromptGuard proxy forwards to and every framework the SDKs hook, with the way to connect each one There are three ways to put PromptGuard in front of an LLM call. Each page in this section says which of them work for that provider or framework. | Way | What you change | What it covers | | - | - | - | | **Proxy** | Your client's base URL, plus an `X-API-Key` header | Any client that speaks the provider's HTTP API, in any language | | **[Auto-instrumentation](/integrations/auto-instrumentation)** | One `init()` call at startup | The provider SDKs the PromptGuard SDKs patch, and frameworks built on them | | **Framework integration** | A handler, middleware or guard added to the framework | LangChain, LangGraph, LlamaIndex, CrewAI, FastAPI and other ASGI apps, and the Vercel AI SDK | The [Guard API](/api-reference/guard) is the fourth option when none of these fit: you send the text, PromptGuard returns a decision, and your code calls the model. ## LLM providers ### How the proxy picks a provider The proxy reads the `model` in your request body and nothing else. There is no provider parameter. 1. **A vendor namespace wins.** A model id that starts with a namespace a provider owns, such as `azure/`, `bedrock/` or `openrouter/`, goes to that provider. The namespace is removed before the request is forwarded, because the vendor does not know it. 2. **Otherwise the first provider that recognises the model family gets it.** `claude-` goes to Anthropic, `gemini-` to Gemini, `gpt-` and the o-series to OpenAI. Each provider page lists the families it claims. 3. **A model no provider recognises is refused** before anything is forwarded. It is never sent to OpenAI as a guess. Rule 2 is checked in a fixed order, so where two providers could claim the same model id, the provider page says which one gets it. For example, `meta-llama/` model ids go to Groq, not Hugging Face. ### Which credential is sent On every proxy route, `X-API-Key` carries your PromptGuard key and `Authorization` carries the provider's key, which PromptGuard forwards. If you have [stored a provider key](/gateway/provider-keys) for the project, PromptGuard sends that one instead and your `Authorization` header is ignored. Each provider page shows the header the provider itself expects, so you do not need to translate it. ## Frameworks This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.