Build your AI API business on a managed LLM upstream

Router One is the managed multi-model upstream you build your own AI API product on. You bring the portal, branding, pricing, and billing — your own one-api / new-api relay or your own app. Router One provides one OpenAI-compatible endpoint for 25+ models, multiple API keys with per-key budgets and rate limits, and per-request usage data so you can bill your own margin on top. The pay-as-you-go token line uses posted model rates, with checkout-visible FX/channel fees kept separate; you set the customer margin.

What you bring vs what Router One provides

Router One is upstream infrastructure, not a white-label product. The line is intentionally clear so you keep full control of your customer relationship.

What you bring

Your own portal, app, or relay (one-api / new-api) — your branding
Your own customer pricing and the margin you charge
Your own billing, invoicing, and customer accounts
Your own signup, support, and terms with your customers

What Router One provides

One OpenAI-compatible endpoint for 25+ models
Multiple API keys per account with per-key budgets (maxSpend) + rate limits
Per-request usage data (model, tokens, cost, latency) to drive your billing
Pay-as-you-go token line at posted model rates, with checkout-visible FX/channel fees kept separate

Why resell on Router One as upstream

Capability	Router One	Opaque relays
Real models, no swapping/downgrading	The model you request is the model served	Often silently downgraded or mixed
Per-request trace to self-verify	Model, tokens, cost, latency, status per request	Little or no per-request visibility
Posted model rates	Posted-rate token line; you set your customer margin	Opaque, bundled pricing
Per-key budgets + rate limits	maxSpend, rate limit, and TPM cap per key	Coarse or account-wide only
Prompt / completion storage	Not retained — metadata only	Often unclear
Models available	25+ models (GPT, Claude, Gemini, DeepSeek, Mistral, Llama)	Varies

Add Router One as a channel to your existing setup

Already running a relay (one-api / new-api) or your own app? Add Router One as one OpenAI-compatible channel — just a base URL and an API key. No SDK swap, no code rewrite. Point your channel at the endpoint below and your existing pricing, accounts, and branding stay exactly as they are.

channel-config

# Add Router One as an OpenAI-compatible channel
Base URL:  https://api.router.one/v1
API Key:   sk-rk-your-router-one-key

Per-key budgets and rate limits do the metering

Create a separate API key per tier, customer segment, or environment. Each key carries its own maxSpend, rate limit, and per-minute token cap, so spend is capped before it runs away — and per-request usage data tells you exactly what to bill. You set your customer pricing in your own portal; Router One just meters the upstream cost accurately.

Reselling vs the referral program

These are two different paths. The referral program pays 5% commission when someone tops up through your invite link — that is affiliate income from sharing a link. Reselling means running your own API business with Router One as the upstream infrastructure: your product, your pricing, your customers, your margin. If you just want to share a link, use the referral program.

See the referral program ->

The transparent alternative to opaque relays

Real models, no swapping

The model you request is the model served — no silent downgrades, no mixing. Your customers get what they paid for, and you can prove it.

No prompt or completion storage

Router One does not retain prompt or completion bodies. Only request metadata (model, tokens, cost, latency, status) is logged for billing, routing, and observability.

Per-request trace to self-verify

Every request carries a trace showing the model, tokens, cost, latency, and status. Verify the served model yourself instead of trusting a black box.

FAQ

Can I resell LLM API access through Router One?

Yes — by building your own product, app, or relay on top. Router One is the managed multi-model upstream: one OpenAI-compatible endpoint for 25+ models, multiple API keys with per-key budgets and rate limits, and per-request usage data. You set your own pricing and branding. Router One does not provide white-label branding or sub-accounts — you bring the portal and the customer relationship.

How do I bill my own customers?

In your own portal or billing system, using the per-request usage data (model, tokens, cost, latency) Router One exposes. Issue a separate API key per customer or tier; each key's maxSpend and rate limit cap usage so no single customer can run away with spend. You charge whatever margin you choose on top of the posted upstream cost.

Is there markup from Router One?

The pay-as-you-go token line uses posted model rates, with checkout-visible FX/channel fees kept separate. You decide the customer pricing in your own portal and keep the spread above your upstream cost.

What's the difference from the referral program?

The referral program is affiliate income: 5% commission when someone tops up via your invite link. Reselling is running your own API business with Router One as upstream infrastructure — your product, pricing, and customers. They are independent paths.

Do you store prompts or completions?

No. Router One does not retain prompt or completion bodies. Only request metadata is logged for billing, routing, and observability.

Build your AI API business on Router One

Get started free