multi-router.aidocs

Providers & Models

Provider Key

Add, configure, rotate, transfer and remove the credentials Multi-Router uses to call model providers.

A provider key is the credential for one of your accounts with a model provider, such as an Anthropic API key or an AWS Bedrock access key, and Multi-Router uses it to call that provider on your behalf. Each provider key belongs to one organization, each organization holds its own keys, and each organization has one default key per provider. Provider keys are created and changed in the dashboard, on the LLM Provider Keys page in the profile menu, or through the API with /v1/provider-keys. Provider key secrets are encrypted at rest and in transit, and a saved secret is never displayed or returned.

Who can manage provider keys

Provider keys are managed by the admins of the organization that holds them. An admin of a named organization adds, edits, disables, deletes, transfers and sets default keys for that organization, and an account admin does the same for the keys held by the account itself. Organization members use the organization's keys through its routers.

The provider keys page

The provider keys page shows every key in the selected organization, grouped by provider. The Providers list on the left shows each provider with its number of keys and the name of its default key, or Not configured when it has none, and selecting a provider shows its keys with a summary such as 2 keys · default production. Each key row shows the following:

LLM Provider Keys

Upstream credentials used to call providers. The default key for each provider is what gets used when a request reaches that provider without a router preset overriding it. Secrets are encrypted at rest; the value can’t be retrieved after creation.

B
AWS Bedrock
2 keys · default Bedrock production
Add AWS Bedrock key
  • Bedrock productionDefault

    Primary Bedrock credentials for production traffic. Owner: platform team. Rotated quarterly.

    wJalrXUtnF••••••••••••••••••••sha256 3f9a2c1e…Created 9/12/2026
    TransferDisableDelete
  • Bedrock stagingDisabled

    Staging account. Disabled after the staging stack moved to us-west-2.

    Kd8xQm2PzR••••••••••••••••••••sha256 b71e04d9…Created 8/30/2026Disabled 9/20/2026
    TransferEnableDelete
The LLM Provider Keys page with AWS Bedrock selected: a default key and a disabled key. Select to enlarge.
ItemMeaning
NameThe key's label.
DescriptionShown below the name when set.
DefaultThe key is the organization's default key for the provider.
DisabledThe key is disabled and serves no requests.
Region badgeThe data residency of an OpenAI key set to US, EU or UAE.
Secret prefixThe first 10 characters of the secret, followed by dots.
sha256The beginning of the secret's fingerprint, with the full value in the tooltip. Two keys that hold the same secret have the same fingerprint.
CreatedThe date the key was added.
Disabled dateThe date the key was disabled, for a disabled key.

Each row offers the following actions:

ActionAvailableEffect
Make defaultOn enabled keys that are not the defaultMakes the key the provider's default key.
EditAlwaysOpens the edit panel.
TransferAlwaysCopies or moves the key to another organization.
DisableOn enabled keysStops new requests from using the key.
EnableOn disabled keysResumes the key's use.
DeleteWhile the key is disabledAsks to confirm, then removes the key permanently. The secret cannot be recovered.

Adding a provider key

Adding a provider key stores a credential for one provider in the selected organization:

  1. Open LLM Provider Keys from the profile menu.
  2. Select the provider in the Providers list. A provider with no keys opens the new-key form directly; otherwise select Add <Provider> key.
  3. Complete the form titled New <Provider> key, then select Save key.
ProviderFields
AnthropicName, API key, Description.
Google GeminiName, API key, Description.
CohereName, API key, Description.
DeepSeekName, API key, Description.
FireworksName, API key, Description.
GroqName, API key, Description.
MistralName, API key, Description.
TogetherName, API key, Description.
xAIName, API key, Description.
Z.aiName, API key, Description.
OpenAIName, Region (Global, United States, Europe or UAE), API key, Description. The Region is the data residency of the OpenAI project the key belongs to.
AWS BedrockAccess key (SigV4) or API key (bearer); Name, AWS Region, AWS Access Key ID, Secret access key or Bedrock API key, Description. See AWS Bedrock.
Google VertexName, Google Cloud project ID, Google Cloud location, Service-account JSON, Description. See Google Vertex.
Custom endpointName, Base URL, API format (OpenAI Chat Completions), API key, Description. See Supported Providers.

Name is required and up to 80 characters, names are labels and can repeat, and Description is optional and up to 2,000 characters. Multi-Router trims spaces from the secret and rejects an empty one, and checks every provider setting when the key is saved. A Google Vertex key is verified with Google when it is saved; the secrets of other providers are checked by the provider, so an invalid secret returns the provider's authentication error on the first request that uses it. A key added while its provider has no default becomes the default.

Obtaining a provider secret

Each provider issues the secret Multi-Router stores. Create a key that only Multi-Router uses:

ProviderWhere to create itTypical prefix
AnthropicClaude Console, Settings, API Keyssk-ant-
OpenAIOpenAI Platform, API keys, within a projectsk-proj-
Google GeminiGoogle AI Studio, Get API keyAIza
CohereCohere dashboard, API Keys (a production key)
DeepSeekDeepSeek Platform, API keyssk-
FireworksFireworks, Settings, API Keysfw_
GroqGroqCloud console, API Keysgsk_
MistralMistral console, API Keys
TogetherTogether, Settings, API Keys
xAIxAI Console, API Keysxai-
Z.aiZ.ai Open Platform, API Keys
AWS BedrockSee AWS Bedrock
Google VertexSee Google Vertex

The default key

The default key is the key an organization uses for a provider when a router names no key. A key added while its provider has no default becomes the default, so the first key for each provider is the default, and Make default on another enabled key of the same provider replaces it. Disabling the default key leaves it as the default, so requests that rely on it fail until it is enabled again or another key is made the default. Deleting the default key makes the oldest enabled key of the same provider the default, and leaves the provider with no default when it has no other enabled key; a key enabled later becomes the default only through Make default.

Which key a request uses

Multi-Router selects the provider key for each request from the router that serves it:

RequestKey used
Static router with a keyThe key set on the router.
Static router set to Org-default keyThe organization's default key for the router's provider.
AliasThe key of the router the alias points to.
Fallback or weighted routerThe key of each member router.
Claude Proxy with organization credentialsThe key set on the Claude Proxy, or, on the Custom route, the key the Claude Proxy assigns to each model in its model group.
Claude Proxy with developer credentialsThe developer's own Anthropic credential, sent with the request.
Adaptive RouterThe key set for the member's provider, or the key set on that member.
Codex Proxy with an organization keyThe OpenAI key set on the Codex Proxy.
Codex Proxy without a keyThe developer's own OpenAI API key, sent with the request.
Gemini ProxyThe Gemini key set on the Gemini Proxy.

Static routers created with POST /v1/routers name a key in routing.provider_key_id, which must be an enabled key of the router's provider in the same organization. Static routers created in the dashboard can select Org-default key instead, which follows the default as it changes, starting with the next request. See Routing.

ExampleResult
Router names openai-prod; the default is openai-devUses openai-prod.
Router set to Org-default key; the default is openai-devUses openai-dev, and openai-prod after Make default on it.
Router set to Org-default key; the default key is disabledReturns provider_key_disabled.
Router names a key that has been deletedReturns router_pinned_key_missing.
Fallback router whose members use different keysEach member uses its own key.

Editing a key

Editing changes a key's details without changing its secret. Edit opens a panel titled Edit <name> with Name and Description, plus Region for an OpenAI key, and Google Cloud project ID and Google Cloud location for a Google Vertex key; select Save to apply it. A changed Vertex project or location is verified with Google before it is saved. The provider, the secret, and the region and credentials of an AWS Bedrock key are fixed; to change them, add a new key.

Rotating a key

Rotating a key replaces it with a new key that holds a new secret, without interrupting requests:

  1. Add a new provider key with the new secret.
  2. If the old key is the default for its provider, select Make default on the new key.
  3. Change every router, Claude Proxy and model group that names the old key to the new key, and change the key in any policy that names it.
  4. Disable the old key and confirm that requests continue to succeed.
  5. Delete the old key, then revoke the old secret with the provider.

With the API, POST /v1/provider-keys/{id}/rotate replaces the secret of a key in place, keeping its id, so routers, Claude Proxies and model groups that name the key need no change.

Disabling and deleting a key

Disabling a key stops Multi-Router from using it while keeping it for later use. Requests already in progress complete, and new requests from routers that name the key, or that rely on it as the default, return provider_key_disabled. A key named by a Claude Proxy can be disabled only after the Claude Proxy's key is replaced or removed. Enabling a Google Vertex key verifies it with Google again.

Deleting a key removes it permanently. A key must be disabled before it is deleted, and a key named by a model in a model group can be deleted only after it is removed from the group. Routers that name a deleted key return router_pinned_key_missing until they are changed to another key.

Copying and moving keys between organizations

Transfer copies or moves a provider key to another organization in the same account. It requires the admin role in both organizations, and an account admin is an admin of every organization in the account.

  1. Select Transfer on the key's row, and choose Copy or Move.
  2. Choose the Destination org. The list shows the organizations in the account where you are an admin, other than the current one, and shows the account itself under the account's name.
  3. Change Name in destination and Description if needed; both start with the key's current values.
  4. Select Copy to <organization> or Move to <organization>.

LLM Provider Keys

Upstream credentials used to call providers. The default key for each provider is what gets used when a request reaches that provider without a router preset overriding it. Secrets are encrypted at rest; the value can’t be retrieved after creation.

B
AWS Bedrock
2 keys · default Bedrock production
Add AWS Bedrock key
  • Move Bedrock production to another org

    copymove
    Cancel
    Destination org
    Research
    org_R4kq8Vn2Ws

    Only orgs in your account. The current org is excluded; keys can’t cross accounts.

    Name in destination
    Bedrock production

    Prepopulated from this key — edit to rename or avoid a clash.

    Description
    Primary Bedrock credentials for production traffic. Owner: platform team. Rotated quarterly.

    Prepopulated; edit freely. The secret is carried over and re-encrypted — never shown.

    This key is moved to the destination and removed from this org. Anything here pointing at it must be repointed.

    This is the default bedrock key here — moving it promotes the next enabled key (or leaves this org with no default).
    An identical key already exists in Research as bedrock-research. You can still proceed — this would be a second copy of the same secret.
    CancelMove to Research
  • Bedrock stagingDisabled

    Staging account. Disabled after the staging stack moved to us-west-2.

    Kd8xQm2PzR••••••••••••••••••••sha256 b71e04d9…Created 8/30/2026Disabled 9/20/2026
    TransferEnableDelete
The Transfer panel moving the default Bedrock key to the Research organization, with the duplicate warning. Select to enlarge.
CopyMove
Source organizationKeeps its key unchanged.The key is removed.
Allowed whenAlways.No router or model group in the source organization names the key. Otherwise the panel lists them.
Source defaultUnchanged.The oldest enabled key of the same provider becomes the default, or the provider has no default.

The secret, provider settings, enabled state and fingerprint carry over. The transferred key becomes the destination's default when it is enabled and the destination has no default for its provider. When the destination already holds a key of the same provider with the same secret, the panel warns An identical key already exists in <organization> as <name>, and the transfer can still proceed.

Security practices

Security practices for provider keys follow from how Multi-Router uses them:

PracticeDescription
Grant inference onlyMulti-Router uses a key only to call models, so create the key with only that permission: the IAM policy on the AWS Bedrock page, the Vertex AI User role on Google Vertex, and a key restricted to model calls where the provider supports it.
Use a key per environmentAn organization holds several keys per provider and each router names its own key, so production and test traffic can use different secrets and be disabled independently.
Keep the secret in your secret managerMulti-Router never displays a saved secret. Record the key's owner and rotation schedule in its Description.
Rotate on a scheduleThe Created date shows each key's age. Rotate with the steps above.
Respond to exposureDisable the key in Multi-Router, which stops new requests from using it, then revoke the secret with the provider.
Check fingerprintsKeys with the same fingerprint hold the same secret, which shows where one secret is used across keys and organizations.

Errors

Requests and router changes return the following errors for provider keys, each with HTTP status 400:

ErrorReturnedCauseResolution
no_provider_key_configuredOn requestsThe router names no key and the organization has no default key for the provider.Add a key for the provider, or select Make default on an enabled key.
provider_key_disabledOn requests, and when saving a router with /v1/routersThe key named by the router, or the default key, is disabled.Enable the key, or change the router or the default to an enabled key.
router_pinned_key_missingOn requestsThe router names a key that has been deleted.Change the router to a current key.
provider_key_mismatchOn requests, and when saving a router with /v1/routersThe key belongs to a different provider than the router's model.Set a key of the correct provider.
provider_key_not_foundWhen saving a router with /v1/routersThe router names a key that is not in the organization.Use a key id from GET /v1/provider-keys.
key_residency_mismatchOn requests and router savesThe region of the router or request differs from the region of its OpenAI key, or the key's region is invalid.Use a key with the matching region, or edit the key.
key_not_foundWhen saving a Claude ProxyThe Claude Proxy uses organization credentials and names no key, a key not in the organization, or a disabled key.Set an enabled key on the Claude Proxy.
key_vendor_mismatchWhen saving a Claude ProxyThe key belongs to a different provider than the Claude Proxy's route.Set a key of the route's provider.
key_region_mismatchWhen saving a Claude ProxyA Bedrock API key was created for a region other than the Claude Proxy's region.Use a key for the Claude Proxy's region, or an access key (SigV4).
credential_not_allowedWhen saving a Claude ProxyDeveloper credentials are used on a route other than Anthropic, or the Custom route names a single key.Use organization credentials, with a key for each model on the Custom route.

The dashboard reports the following when a key action is refused:

ActionRefused when
AddA required field is empty, a field is too long, or a provider setting is invalid, such as a Bedrock region or a Vertex service account Google does not accept.
EditA field is too long, or a changed Vertex project or location fails verification.
Make defaultThe key is disabled, a Vertex key fails verification, or the default changed at the same time.
EnableA Vertex key fails verification.
DisableA Claude Proxy names the key.
DeleteThe key is enabled, a Claude Proxy or model group names it, or it changed at the same time.
TransferThe destination is the current organization, you are not an admin of both organizations, or, for a move, a router or model group names the key.

Managing keys with the API

The /v1/provider-keys endpoints act on the provider keys of the API key's organization. Reads never return a secret; a create or rotate returns the new secret once. Scopes are cumulative: provider_keys:delete includes write, and write includes read.

MethodPathDescriptionScope
GET/v1/provider-keysList keys, including disabled keys, paged with limit (1 to 200, default 50) and cursor.provider_keys:read
POST/v1/provider-keysAdd a key from name, provider, secret and the provider's settings. Accepts dry_run.provider_keys:write
GET/v1/provider-keys/{id}Get one key.provider_keys:read
PATCH/v1/provider-keys/{id}Change name, description, enabled, is_default, the Bedrock region, the Vertex project and location, or the OpenAI region. Accepts dry_run.provider_keys:write
POST/v1/provider-keys/{id}/rotateReplace the secret, keeping the key id.provider_keys:write
POST/v1/provider-keys/{id}/transferCopy or move the key to another organization.provider_keys:write; a move also provider_keys:delete
DELETE/v1/provider-keys/{id}Delete a disabled key that nothing uses.provider_keys:delete

Each key has its id, prefixed llpk_, used in provider_key_id, with name, description, provider, key_prefix, enabled, is_default, its etag, and the provider's section: bedrock with region, auth_mode and access_key_id; vertex with project_id and region; openai with data_residency; or custom with base_url and api_format. See Provider Keys in the API Reference for every field and error.

Requestbash
curl "https://api.multi-router.ai/v1/provider-keys?limit=50&cursor=$NEXT_CURSOR" \
  -H "Authorization: Bearer $MR_API_KEY"
Response 200json
{
  "organization_id": "org_7Tq2Wd9KxP",
  "data": [
    {
      "id": "llpk_4Vd8Qm2RtL",
      "object": "provider_key",
      "name": "Bedrock production",
      "description": null,
      "provider": "bedrock",
      "bedrock": { "region": "us-east-1", "auth_mode": "sigv4", "access_key_id": "AKIAIOSFODNN7EXAMPLE" },
      "key_prefix": "wJalrXUtnF",
      "enabled": true,
      "is_default": true,
      "etag": "\"3\"",
      "created_at": "2026-09-12T17:47:43Z",
      "updated_at": "2026-09-30T08:12:09Z"
    }
  ],
  "next_cursor": null,
  "has_more": false
}
Supported ProvidersRegions & Variants
Was this helpful?