multi-router.aidocs

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.

  1. Sign in to the dashboard at https://dashboard.multi-router.ai.
  2. Open LLM Provider Keys from the profile menu at the top right, and select Anthropic in the Providers list.
  3. 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.

  1. Open Routers in the top navigation, and select New router.
  2. Under Type, keep Static Router, which is selected.
  3. Under Details, name the router, such as Support bot.
  4. 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.
  5. 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.

  1. Open API Keys from the profile menu, and select New API key.
  2. Name the key, such as quickstart, keep the Inference only access, and select Create.
  3. 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:

Requestbash
curl https://api.multi-router.ai/v1/chat/completions \
  -H "Authorization: Bearer $MR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "multi-router/rt_9Hk3Ws7PzQ",
    "messages": [{ "role": "user", "content": "Say hello in one sentence." }]
  }'

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:

GoalPage
Use the OpenAI or Anthropic SDKUsing an SDK
Add a fallback providerFallback Router
Attach a system prompt to the routerPrompt Binding
Give each application its own limited keyRouter Access
Cap spendCreating a Budget
Connect Claude CodeClaude Code
OverviewUsing an SDK
Was this helpful?