starter.wikiSearch⌘K

Hosted multi-model routing and billing

OpenRouter

A hosted API that aggregates model and provider routes, centralizes credits or BYOK, and exposes provider selection, fallback, and privacy controls.

Visit official site

Editorial verdict

Choose OpenRouter when hosted model and provider choice is more valuable than direct-provider control, after governing fees, credits or BYOK, routing, provider logging, retention, and fallback behavior.1234

Best for

  • Rapid multi-model evaluation
  • Hosted provider routing and fallback
  • Teams accepting centralized credits or governed BYOK
1234

Not ideal for

  • Teams requiring self-hosted gateway control
  • Products unable to evaluate upstream provider policy
  • Buyers treating all provider routes as equivalent
1234
Main trade-off

Broad hosted model access reduces integration work while adding aggregator fees, credits, provider-routing, privacy, availability, and another commercial dependency.1234

Product boundary

Whether OpenRouter's hosted aggregation, credit or BYOK billing, provider routing, and privacy controls fit the model-selection and data boundary.

OpenRouter is a hosted model aggregation and routing service, not a self-hosted gateway. OpenRouter's own logging defaults do not determine each upstream provider's retention, training, region, or policy; provider input access remains part of the route.1234

For: Teams wanting rapid access to many hosted models through one commercial and routing surface

  • The production workload, language, model, provider, or deployment boundary changes
  • Current pricing, retention, data use, policy, or regional support changes
  • Measured quality, latency, reliability, or operating cost no longer fits

Why teams consider OpenRouter

  • Model catalogOne API surface exposes many model and provider routes.1234
  • Routing controlsProvider ordering, requirements, fallbacks, and policy filters can influence selection.1234
  • Billing choiceOpenRouter credits and BYOK have distinct fee and operational boundaries.1234

Pricing

Provider inference is generally passed through at the selected route's rate, while credit purchases and BYOK requests have separate OpenRouter fee rules.1

Current official route

Pay-as-you-go credits or BYOK

Verified 2026-07-27: OpenRouter documents a fee when purchasing credits and a separate BYOK allowance and fee model. Selected provider inference and policy remain part of the total decision.1

Credits
OpenRouter purchase fee plus provider inference deducted from balance1
BYOK
Separate allowance and fee rule with direct provider credentials1
Provider boundary
Availability, routing, retention, training, region, and policy vary by upstream route1
Pricing checked View official pricing

OpenRouter vs alternatives

Portkey

Choose when
Choose Portkey when a managed AI control plane removes meaningful routing and governance work, after modeling provider bills, gateway traffic, recorded logs, retention, privacy, and deployment.
Avoid when
Teams requiring a self-operated gateway by default
Compared with OpenRouter
A managed control plane centralizes reliability and governance while adding request, log, retention, data, deployment, and platform dependence on top of provider inference.56

LiteLLM

Choose when
Choose LiteLLM when a self-operated proxy boundary is a requirement and the platform team can own reliability, credentials, upgrades, telemetry, policy, and provider-specific compatibility.
Avoid when
Teams without a critical-proxy operator
Compared with OpenRouter
Open-source proxy control reduces application coupling while transferring availability, security, upgrades, logging, compatibility, and provider-change response to the platform team.78

Vercel AI Gateway

Choose when
Choose Vercel AI Gateway when its managed endpoint and provider operations reduce meaningful work, after verifying current pricing, credits, BYOK, failover, provider order, and ZDR eligibility.
Avoid when
Teams requiring a self-operated gateway
Compared with OpenRouter
A managed Vercel gateway simplifies provider access and failover while adding gateway, credit, catalog, routing, data-policy, and platform dependence.910

Resources and sources

Official product, documentation, pricing, and policy sources

  • OpenRouter pricing and billing FAQ
    Open
  • OpenRouter provider routing
    Open
  • OpenRouter provider logging controls
    Open
  • OpenRouter privacy policy
    Open
  • Portkey pricing
    Open
  • Portkey AI Gateway documentation
    Open
  • LiteLLM pricing
    Open
  • LiteLLM proxy documentation
    Open
  • Vercel AI Gateway product and pricing
    Open
  • Vercel AI Gateway documentation
    Open
  1. 1
    OpenRouter pricing and billing FAQ

    OpenRouter · Accessed Official

  2. 2
    OpenRouter provider routing

    OpenRouter · Accessed Official

  3. 3
    OpenRouter provider logging controls

    OpenRouter · Accessed Official

  4. 4
    OpenRouter privacy policy

    OpenRouter · Accessed Official

  5. 5
    Portkey pricing

    Portkey · Accessed Official

  6. 6
    Portkey AI Gateway documentation

    Portkey · Accessed Official

  7. 7
    LiteLLM pricing

    LiteLLM · Accessed Official

  8. 8
    LiteLLM proxy documentation

    LiteLLM · Accessed Official

  9. 9
    Vercel AI Gateway product and pricing

    Vercel · Accessed Official

  10. 10
    Vercel AI Gateway documentation

    Vercel · Accessed Official