> For the complete documentation index, see [llms.txt](https://docs.interactive.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interactive.ai/connectors/router.md).
# Router
The Router is a single OpenAI-compatible endpoint in front of every model the platform can reach. Your application calls one URL with one key and names the model it wants, so changing model becomes a string change rather than a new integration.
Because every call passes through the platform, cost and latency are recorded against the model definitions in this catalog with no instrumentation on your side. Agents use the Router as well: the primary and fallback models on an agent's Connections step are chosen from the same catalog.
### The model catalog
LLMs lists every model reachable through the Router, with the Model ID your calls use, the upstream provider, the region, what the model is suited to, its capabilities and context window, and its pricing.
These definitions are maintained by InteractiveAI, so pricing and tokenization stay current as providers change their rates and you never configure either.
The same model can appear once per region, so filter by region when it matters where a request is served.
Opening a model shows its match pattern, the expression the platform uses to recognise it in your traces, along with its tokenizer and full pricing per million units. Below that, Model observations lists every generation that used the model, with the same filters and export controls as Observability. That is where you see how a model actually performs in your project rather than how it is advertised.
### Router keys
A Router key is what your application authenticates with. It is shown once when created, so copy it then, and it is sent as a bearer token to the Router's chat completions endpoint. The dialog that creates it includes a ready-to-run request so you can confirm the key works before wiring it into anything.
Each key carries a spend limit and a reset period, and the list shows how much of the limit remains. That makes a key a unit of budget control as well as authentication: give an application or a team its own key and cap what it can spend. Agents get their own key generated when you deploy them.
---
# 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.interactive.ai/connectors/router.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.
