Skip to content
AnyRouter

Models Catalog

Browse models you can call in your workspace, with pricing, context limits, capabilities, and active-use signals. Show all models lists the full catalog.

Picking a model shouldn't mean cross-referencing a dozen provider pricing pages. The Models page is the single source of truth for models you can call through AnyRouter — what's available with your current keys and settings, what each model can do, how much it costs, and which models your workspace has actually used. Open it from the dashboard sidebar, the public /models catalog, or /dashboard/models.

By default the list hides models you cannot reach (for example Anthropic Sonnet when you have no Anthropic or OpenRouter BYOK key). Turn on Show all models (or add ?all=1 to the URL) to browse the full catalog. The same rule applies to GET /api/v1/models.

Overview

Each row in the catalog represents one model and exposes the fields you need to decide without leaving the page:

FieldWhat it tells you
Model idThe canonical string you pass in the model field (for example openai/gpt-5.4-mini, anthropic/claude-sonnet-4.6, z-ai/glm-4.7-flash). This is what matters in code.
Display nameA human-friendly label rendered alongside the id when one is set.
Owner organizationThe company that trained and publishes the model (OpenAI, Anthropic, Google, Meta, Mistral, Z-AI, and so on), shown as a logo and name so you can scan by vendor.
Provider badgeThe upstream that serves the request. AnyRouter ships a single unified gateway badge, so you don't need to pick a provider to start using a model.
Context windowMaximum total tokens (prompt plus response) per request. Larger windows let you pass more, but tokens still count toward your bill.
Max outputMaximum tokens the model can emit in one response. A max_tokens set higher is clamped down silently for you.
PricingInput and output cost, in US dollars per 1 million tokens. Free-tier models show Free.

Context limits are shown in raw token counts so you can compare exact limits across vendors without doing your own conversion.

How it works

Pricing

Prices are US dollars per 1M tokens, broken into Input (prompt tokens you send) and Output (completion tokens returned). A request using 12,000 prompt tokens and 800 output tokens against a 1.00 / 4.00 model costs 12000/1_000_000 * 1.00 + 800/1_000_000 * 4.00 ≈ $0.0152 — the same arithmetic AnyRouter does at billing time, with cache-hit and cache-write rates applied on top when supported (see Prompt Caching). Where a model supports differentiated cache rates, those appear as smaller rows under the headline price.

Prices shown are the all-in rate you're billed per token. There are no separate per-request fees on top.

Capabilities

Every model exposes a row of capability chips so you know what it supports before you write code:

  • Tools / function calling — accepts a tools array and returns tool calls.
  • Vision — accepts image content parts (image_url or base64 data URLs).
  • Structured output — honors response_format: { type: "json_schema", ... } and returns a conforming payload.
  • Streaming — can be invoked with stream: true to receive server-sent events.
  • Prompt caching — can cache long prompt prefixes between requests (see Prompt Caching).
  • Multilingual — rated strong on non-English inputs.

A missing capability is grayed out, so you don't have to guess.

"Active in your workspace" filter

By default the catalog already hides models you cannot call. The Active in your workspace filter narrows the remaining list to models you're actually calling. A model counts as active when, in the last 30 days, any of these is true:

  • A request from one of your API keys was successfully routed to the model.
  • A preset in your workspace references the model.
  • The model was selected as the default for an API key.

The "last 30 days" window matches the rolling usage window used elsewhere in the dashboard (Usage, Logs, Credits). It's useful for auditing which models a team actually uses, mirroring the Usage breakdown, and trimming presets. Toggle it off any time to discover something new — for example a smaller, cheaper variant of a model you already use. It updates within a few minutes of a successful request.

Privacy badges

Each row includes a privacy tier badge for its serving provider:

  • Zero-retention — the provider doesn't log prompts or completions beyond what's required to serve the request.
  • Short-retention — limited retention (typically for abuse detection), with no training on your data.
  • Standard — the provider may retain data longer and may use it for service improvements unless you opt out.

The badges are advisory — they reflect the upstream's public commitments at the time the model was added. If you have hard requirements, use Privacy controls to block providers you don't want.

See Privacy Controls for the full provider list, how blocks are enforced, and what happens to requests that resolve to a blocked upstream.

Aliases and routing

The model id in the catalog is the canonical id. AnyRouter also accepts:

  • Aliases — shorter names that resolve to a canonical id (for example, vendor-shipped shortcuts).
  • AnyRouter virtual aliases — catalog ids such as anyrouter/auto, anyrouter/latest, and anyrouter/free that resolve at request time to a chain of concrete models. anyrouter/latest picks the latest stable production chat model that is actually serving traffic (not a preview SKU, not an unused catalog entry); see Smart Routing.
  • Presets — workspace-defined virtual models that bundle a base model with parameters and system instructions, referenced as @preset/<name> and combinable with a model override: openai/gpt-5.4-mini@preset/code-reviewer.
  • Per-request provider preferences — pin a request to a specific upstream, sort by price or latency, or set a maximum price via a provider object in the request body.

Workspace presets don't appear in the catalog as models — they're listed on the Presets page. Built-in anyrouter/* aliases do appear, because the id you copy is callable on its own. For the full set of routing rules, see Smart Routing.

Configure

Trying a model

Every catalog row has a Copy action that copies the model id to your clipboard. A minimal smoke test:

curl https://anyrouter.dev/api/v1/chat/completions \
  -H "Authorization: Bearer sk-ar-your-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-5.4-mini",
    "messages": [
      { "role": "user", "content": "Reply with the single word: ready." }
    ]
  }'

Swap openai/gpt-5.4-mini for any id you copied. The same id works in the OpenAI Python and Node SDKs pointed at https://anyrouter.dev/api/v1. For streaming, add "stream": true and consume the response as server-sent events. If a model doesn't respond as expected, check Logs in the dashboard for the request id — you'll see exactly which upstream served the call and the error code returned.

Programmatic access

To get the catalog data in code — for a model picker, internal docs, or a cost calculator — call the public models endpoint instead of scraping the dashboard:

curl https://anyrouter.dev/api/v1/models \
  -H "Authorization: Bearer sk-ar-your-key"

The response is OpenAI-compatible and includes the model id, owner, context window, pricing, and capability flags for every model the current caller can reach. A typical workflow: browse the catalog to find candidates, hit /api/v1/models from your app at runtime, cache the response for a few minutes (the catalog changes rarely), and use the returned id strings directly in your requests. Pass ?all=1 when you need the full catalog regardless of keys. See the Models API reference for the full schema and filters.

Frequently asked questions

Why does a model I expect to see not show up?

The default list only includes models you can call with the current session or API key. BYOK-only models stay hidden until you add a matching key; privacy blocks and empty local-relay pools also omit rows. Turn on Show all models (or call /api/v1/models?all=1) to see the full catalog. If a model is still missing there, it may have been removed by its upstream — check Logs for recent attempts.

Do prices in the catalog include AnyRouter fees?

Yes. The prices shown are the all-in rate you're billed per token. There are no separate per-request fees on top.

Can I see when a price changed?

Price changes are announced in advance and recorded in your Credits transaction history once they take effect. The catalog always reflects the current rate.