> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/merge-gateway/embedded-routing-stack/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Embedded Routing

> Build once. Connect to every API, tool, and LLM. Ship products and agents to production without owning the integration stack.

## Docs

- [Embedded Routing Stack](https://docs.merge.dev/merge-gateway/embedded-routing-stack/overview.md): Provision each of your end customers with their own routing policies, vendor keys, budgets, guardrails, and usage through the /v1/customers API, and scope requests to a customer at request time.
- [Customers](https://docs.merge.dev/merge-gateway/embedded-routing-stack/customers.md): Create, look up, update, deactivate, and delete Customer objects, the end customers you scope Embedded Routing requests to.
- [Routing policies](https://docs.merge.dev/merge-gateway/embedded-routing-stack/routing-policies.md): Create per-customer routing policies with a ranked priority list or an intelligent strategy, and choose which one is the customer's default.
- [Customer keys](https://docs.merge.dev/merge-gateway/embedded-routing-stack/customer-keys.md): Add, rotate, and remove a customer's own bring-your-own-key vendor credential, and choose which credentials may serve that customer.
- [Customer API keys](https://docs.merge.dev/merge-gateway/embedded-routing-stack/customer-api-keys.md): Mint a Merge Gateway API key scoped to one customer, so every request it makes is attributed and enforced for that customer with no customer field.
- [Budgets](https://docs.merge.dev/merge-gateway/embedded-routing-stack/budgets.md): Set a per-customer spend limit that blocks requests once exhausted, or a soft limit that keeps serving.
- [Guardrails](https://docs.merge.dev/merge-gateway/embedded-routing-stack/guardrails.md): Set sparse per-customer prompt injection and DLP overrides on top of your organization's policy, and learn when a relaxed override actually applies.
- [Usage](https://docs.merge.dev/merge-gateway/embedded-routing-stack/usage.md): Read a customer's spend over a date range, split by who supplied the credential and broken down by model, provider, and routing policy, or pull one record per request to bill in your own system.