Getting Started
Quickstart
Sending a first request through Multi-Router: a provider key, a router, an API key and a request.
This quickstart sets up a router for an Anthropic model and sends it a request. It takes a Multi-Router account and an Anthropic API key. Other providers follow the same steps, with the extra settings some need, such as a region for AWS Bedrock.
1. Add a provider key
A provider key is the organization's credential for a model provider, which Multi-Router uses to send requests there.
- Sign in to the dashboard at
https://dashboard.multi-router.ai. - Open LLM Provider Keys from the profile menu at the top right, and select Anthropic in the Providers list.
- In the form, or with Add Anthropic key, enter a Name, such as Anthropic production, paste the API key, and select Save key.
The first key for a provider becomes its default key. See Provider Key.
2. Create a router
A router holds the model and settings a request is served with.
- Open Routers in the top navigation, and select New router.
- Under Type, keep Static Router, which is selected.
- Under Details, name the router, such as Support bot.
- Under Routing, choose the model, such as Claude Sonnet 4.5, its provider Anthropic and variant standard, and the key from step 1, or Org-default key.
- Under Review & create, create the router, and copy its id with Copy router ID, such as
rt_9Hk3Ws7PzQ.
See Static Router.
3. Create an API key
An API key authenticates your application to Multi-Router.
- Open API Keys from the profile menu, and select New API key.
- Name the key, such as quickstart, keep the Inference only access, and select Create.
- Copy the key with Copy, and set it in your shell as
MR_API_KEY.
See API Key.
4. Send a request
Send a Chat Completions request that names the router in the model field:
The response is a standard Chat Completions response, with headers such as x-mr-provider and x-mr-upstream-model showing how it was served.
5. See it in Traffic
Open Traffic in the top navigation. The request appears at the top, with its router, model, tokens, cost and latency, and selecting its request id opens its full detail. See Traffic.
Next steps
Each next step builds on the router and key from this quickstart:
| Goal | Page |
|---|---|
| Use the OpenAI or Anthropic SDK | Using an SDK |
| Add a fallback provider | Fallback Router |
| Attach a system prompt to the router | Prompt Binding |
| Give each application its own limited key | Router Access |
| Cap spend | Creating a Budget |
| Connect Claude Code | Claude Code |