API reference

The production base URL for OpenAI-compatible clients is:

https://api.anonrouter.ai/v1

That is the only URL ordinary tools such as OpenCode, SillyTavern, and OpenAI SDK clients need. The private ticket flow additionally uses:

https://control.anonrouter.ai/v1

The control origin receives keys and content-free account or authorization requests. The confidential API origin receives inference content and attestation requests. The AnonRouter SDK keeps the two origins separate automatically.

Requests authenticate one of three ways, depending on the endpoint:

• Inference key (ar_) in Authorization: Bearer to issue tickets and, in compatibility mode, to call inference directly.
• Management key (arm_) in Authorization: Bearer to read balance and usage.
• Inference ticket in the x-anonrouter-ticket header to run a single ticketed request.

Some account and billing operations require an authenticated session and are performed from the dashboard rather than with an API key.

Inference

/models/uptime requires a ?model=<id> query parameter and answers 400 missing_model without one.

In compatibility mode, /chat/completions and /embeddings accept an inference key directly instead of a ticket.

Attestation

See TEE verification for what each document proves.

The routing, account, workspace, billing, and key-management endpoints below are control-plane operations and use https://control.anonrouter.ai/v1 unless the page says otherwise.

Routing

Account

Workspaces

Connected Apps

Connected Apps uses a focused OAuth 2.1 and OpenID Connect provider. Begin with the discovery document at https://control.anonrouter.ai/connect/.well-known/openid-configuration instead of hard-coding the authorization, token, UserInfo, revocation, or JWKS paths. See Connected Apps for the complete user and developer flow.

The dashboard uses these session-authenticated management endpoints:

Billing

Response headers

Successful inference responses include:

• x-anonrouter-selected-model: the chosen provider/model.
• x-anonrouter-routing: auto or exact.
• x-ratelimit-limit-requests, x-ratelimit-remaining-requests, x-ratelimit-reset-requests, and the matching -tokens variants.

Errors

Errors use an OpenAI-style envelope with a machine-readable type and a request_id:

{
  "error": {
    "message": "Inference ticket is invalid or expired",
    "type": "invalid_ticket",
    "request_id": "req_..."
  }
}

Common cases:

A 429 response also sets a retry-after header. During streaming, a mid-stream provider failure is delivered as an inline SSE error frame rather than an HTTP status, because the response headers have already been sent.