Hosted routing plans

One subscription for Sage Router control plane access.

Use the hosted edge at https://api.sagerouter.dev/v1 for account-managed API keys, quotas, fallback reliability, and routing telemetry while keeping provider access customer-authorized and local-first by default.

Start API key activation Read quickstart View public status Billing help Fusion Compare gateways Compare OpenRouter Estimate savings See launch plan

Sage Router sells routing, reliability, account management, quotas, analytics, and support. It does not grant unauthorized model access, pool provider accounts, or bypass provider terms.

Fastest API key start: email yourself the setup link

No provider key or credit card is required until your generated sk_sage_* key exists. Continue with GitHub or email; both open the hosted account page with Pro selected, then you can create the key first and complete checkout.

Copy setup first. Paste the bundle now, then replace the placeholder with your generated sk_sage_* key after Pro setup. Create API key next

Already signed up but no sk_sage_* key?

Skip plan comparison and reopen the generated-key setup path. It preserves the key-first flow and records this as recovery demand.

Finish setup key Use email/password fallback

1. Copy setupPut the OpenAI-compatible endpoint into your agent config first.

2. Generate keyCreate an sk_sage_* key from the browser account flow.

3. Verify routeTest /v1/models, then send the first hosted request.

Key-first activation proof

Create the key before checkout.

The Pro handoff opens generated-key creation first. That gives a buyer the setup artifact before payment, then checkout unlocks hosted routing once the account is active.

Create API key first Verify with the quickstart

Lite

$6 / month

For individual agent experiments and lightweight hosted routing.

10,000 included requests per month
60 requests per minute
Hosted API keys and basic usage visibility
Standard fallback chains

Start Lite

Pro

$30 / month

For daily AI agent work, frontier profiles, and practical fallback policy.

50,000 included requests per month
180 requests per minute
Agentic, frontier, and Fusion route profiles
Analytics snapshots and route telemetry

Start API key setup

Max

$72 / month

For higher-volume automation, teams, and priority routing capacity.

200,000 included requests per month
600 requests per minute
Priority fallback and Fusion budget
Team and private deployment support path

Start Max

Launch math

A credible path to $10k MRR.

The hosted plan ladder is designed to reach a real SaaS target without pretending Sage Router is a model resale marketplace. A mixed cohort of 100 Lite, 200 Pro, and 50 Max customers is $10,200 MRR.

Customer mix	Monthly recurring revenue	What it proves
334 Pro	$10,020	Daily agent developers value hosted routing and analytics.
139 Max	$10,008	High-volume teams pay for reliability and priority capacity.
100 Lite + 200 Pro + 50 Max	$10,200	Balanced conversion across hobby, professional, and team use.

What customers buy

Hosted convenience without losing control.

Generated sk_sage_* API keys for OpenAI-compatible clients.
Supabase-backed account login, Stripe checkout, and self-service billing.
Public edge routing with anonymous model traffic blocked by default.
Usage quotas, request-per-minute limits, route telemetry, and fallback health.
Tailnet/private-router resilience for teams that keep provider credentials on their own hosts.

Managed provider access

A guarded path toward one subscription for bundled model access.

Managed provider access is not active in the public plans yet. It will stay disabled until Sage Router has explicit provider resale terms, a published margin policy, durable quotas and rate limits, durable operator audit events, and acceptable-use terms for managed model access.

Default launch: customer-authorized providers and local models.
OpenRouter remains supported for customer-authorized BYOK routing, not bundled public resale.
OpenRouter-specific buyers can review the Sage Router vs OpenRouter page before choosing a hosted marketplace API, local-first routing layer, or both.
Future path: private-beta managed access after contract, billing, and abuse-control readiness checks pass.
Readiness is exposed in the public /pricing metadata as managedProviderAccess.
Positive unit economics must be backed by a configured cost model and plan-margin checks before bundled model access can become active.
Prerequisite boundaries are published as provider resale terms, a margin policy, and acceptable use.

Request Max implementation review Start Max with BYOK

Beta interest and implementation review are demand capture only. Public checkout still buys Sage Router routing, account, quota, analytics, and reliability infrastructure.

Runtime guard

Live managed-access readiness checkpoint.

Disabled pending provider terms

The public API keeps managed provider access disabled until provider resale terms, an allowlist, margin policy, configured cost model, plan-margin checks, quotas, audit events, and acceptable-use controls are all ready.

6 missing controls

Not configured provider cost model

Not satisfied unit economics

Plan	Public revenue / 1k requests	Max safe provider cost / 1k	Managed-access margin status
Lite	60 cents	39 cents	Waiting on provider cost model
Pro	60 cents	39 cents	Waiting on provider cost model
Max	36 cents	23.4 cents	Waiting on provider cost model

Provider family	Managed access status	Boundary
Ollama	Not allowlisted	Eligible only after provider authorization, cost, quota, audit, and abuse controls
OpenAI	Not allowlisted	Eligible only after provider authorization, cost, quota, audit, and abuse controls
Anthropic	Not allowlisted	Eligible only after provider authorization, cost, quota, audit, and abuse controls
OpenRouter	BYOK supported; not bundled resale	Supported routing provider, but not part of the managed subscription offer

oneSubscriptionReadiness keeps the commercial preference visible while providerFamilyReadiness keeps OpenRouter available as BYOK routing without bundling it into managed resale.

provider_resale_terms provider_terms_acknowledgment authorized_provider_allowlist margin_policy provider_cost_model positive_unit_economics

This checkpoint is public metadata only. It does not expose provider credentials, costs, OAuth tokens, customer prompts, raw responses, or generated API keys.

OpenRouter and other BYOK-compatible gateways can be routed with authorized customer keys, but they do not satisfy the managed resale allowlist.