Router One for companies: payment, invoices, contracts and usage limits (and what we don't offer)

Who this fits, and when to look elsewhere

For the technical lead

What changes in your stack, how usage is separated, and where the reliability evidence lives.

• Endpoint: one OpenAI-compatible base URL, https://api.router.one/v1, for 30+ models; Anthropic-compatible clients such as Claude Code use the host root https://api.router.one. Which endpoint serves which model family is in /docs.
• Routing: requests are served by the model you name; a failing route (429, 5xx, timeout) is retried on another route for the same model, and routes with a sustained upstream-error rate move to the back of the order until they recover.
• Keys: an account can hold many API keys. Each key has a name, an optional expiry date and an optional spend cap (maxSpend), set in Dashboard → API Keys, so each person, service or environment can have its own key.
• Company accounts with multiple members (one company payer, each member on their own keys) are coming soon, with no launch date yet; today, use one account with one key per person.
• A key's spend cap (maxSpend) limits what that key can charge to your wallet: once its cumulative wallet charges reach the cap, its wallet-billed requests return HTTP 402. Requests covered by your plan's quota draw from the account's shared plan quota and do not count toward any key's cap.
• To stop a key completely, including plan-covered requests, delete it. Expired keys that have not been deleted still count toward the account's active-key limit, so delete a person's keys when they leave.
• The console sends an in-app notification when a key reaches 80% of its maxSpend and again when it hits the cap (key-cap notices are in-app only, and there are no webhook alerts).
• No low fixed cap for normal paid usage. Each key and each account runs under default request-per-minute and token-per-minute limits, and upstream constraints may still apply; if a request returns 429, back off and retry (honor Retry-After when it is sent), and if your traffic needs higher limits, email support@router.one to have the key or account limits raised.
• Reliability evidence: each model page linked from /models publishes 7-day and 30-day panels (successful-response share, terminal 429 and 5xx rates) once a window holds at least 100 requests from at least 5 callers, and https://router.one/status lists active incidents and an API reachability probe re-run at most hourly. No platform-wide uptime percentage is published.
• Price changes: the rates on /models are the rates you are billed at, and material increases are announced at least 7 days in advance in the changelog and in Dashboard announcements (/pricing-methodology).

For finance

How money moves, what paperwork you get, and how to reconcile spend.

• Payment: Top up with a card or Alipay through one hosted checkout, or with USDT/USDC on six chains (Tron, BSC, Ethereum, Polygon, Base, Arbitrum). No US credit card required.
• Minimum top-up: The checkout page is the source of truth for the minimum amount. Card and Alipay top-ups currently usually start at $5 USD equivalent; RMB amounts are converted and shown at checkout using the current FX rate. Stablecoin top-ups usually start at $5 USD equivalent.
• Wallet: the balance is in USD, billed per token, and never expires. It never recharges itself: there is no automatic recharge and no top-up API, so every top-up is made in the dashboard.
• Plans: Pro $20.19, Max $47.99 and Ultra $149 per 30-day cycle, bought per account (see /pricing). Every key on the account draws the same tier quotas, and usage beyond them bills to the wallet at posted rates. A plan paid by card renews monthly until canceled; a plan paid from wallet balance covers one period and does not renew.
• Invoices: every payment through the hosted checkout (card or Alipay) is invoiced automatically; the invoice is emailed to the checkout address once the payment succeeds, for wallet top-ups and plans alike, so there is nothing to request. These are not Chinese VAT invoices (fapiao), and stablecoin top-ups are not invoiced.
• Refunds: purchased credits are non-refundable once added to your balance, except for billing errors on our side or where required by law, so start with a small top-up (https://router.one/refund).
• Reconciliation: Dashboard → Logs filters by API key and exports the filtered rows to CSV (request ID, model, key, tokens, cost, total time, time to first token where recorded, status), and the wallet ledger exports to CSV for a chosen range; up to 100,000 rows per export (a larger export is refused: narrow the date range and export in parts). Dashboard → Usage ranks your keys by spend, tokens and requests.
• Balance from your server: GET https://api.router.one/v1/balance returns the account's prepaid balance in USD with any key of the account, under its own 60-requests-per-minute limit. When the wallet is empty, requests that need the wallet return HTTP 402.
• Rates: Router One does not publish self-serve volume tiers. Pricing starts as low as 10% of official provider list prices (up to 90% off) on select models; live per-model rates: https://router.one/models

For security and legal

Who may use the keys, what is logged, and what Router One does not sign today.

• Sign-in: email, Google or GitHub. There is no SSO/SAML and there are no member roles; one login owns the account, its wallet and its keys.
• Who may use the keys: under the Terms (https://router.one/terms), you may issue keys to your own employees and to contractors working on your behalf, and use keys server-side inside services you run for your customers. Keys stay under your control: never publish them or hand them to third parties for their own use. The account holder is responsible for all usage under the account.
• Key storage and transport: keys are stored hashed, plus an encrypted copy so you can reveal a key again in Dashboard → API Keys; all traffic is over TLS 1.2+ (https://router.one/security).
• Logs: Dashboard → Logs records request metadata (model, request ID, tokens, cost, latency and status). It does not show which supplier or route served a request.
• Data retention: what is kept, for how long, and how to request deletion is on https://router.one/data-retention. Send a deletion request from the account owner's email address.
• Upstream processing: to produce a response, each request is sent to an upstream provider of the model you call; Router One does not name its suppliers.
• Model IDs with a sales-channel prefix (azure/, aws/, vertex/, aistudio/) are separately priced products of the same base model; they carry no region, data-residency or compliance commitment.
• Not offered: a DPA, compliance certifications (such as SOC 2 or ISO 27001), an audit log or a data-residency commitment.
• Contracting party: this site does not list a contracting company today; for an annual contract, email support@router.one with the subject "Annual contract".
• SLA: pay-as-you-go and subscription accounts get the same failover but no contractual SLA; a written SLA with service credits is available only under an annual enterprise agreement (https://router.one/sla).

For partners and resellers

Annual terms, building your own service on Router One, and referrals.

• Annual contract: email support@router.one with the subject [Business] Annual contract and your expected monthly spend.
• Building your own service on Router One is self-serve: you bring the portal, branding, pricing and customer billing; Router One provides one OpenAI-compatible endpoint, per-key spend caps and per-request usage data at posted rates. Give each downstream customer its own key and use it server-side inside your service (https://router.one/llm-api-reseller).
• Router One bills you at posted rates and publishes no wholesale tiers; how you price and bill your own customers is up to you.
• Referrals: the referral program pays a commission on referred users' top-ups (5% by default; your dashboard shows your exact rate), credited to your wallet balance and spendable on model usage; withdrawals are not supported today (https://router.one/referrals).

What Router One does not offer (as of 2026-10-23)

Every item below was checked on 2026-10-23. If one of them is a hard requirement for your company, Router One is not the right fit today.

Try it for a week before you commit

Purchased credits are not refundable, so test with a small amount first:

1. Top up a small amount; the minimum is shown at checkout.
2. Create one key per environment (for example development, staging and production), each with a spend cap and an expiry date a week or two out.
3. Point a real workload at the base URL (your existing OpenAI SDK code, Claude Code or Codex) and run the traffic you plan to run in production.
4. Export Dashboard → Logs to CSV, filtered by key, and check tokens and cost against your own records; Dashboard → Usage ranks the keys by spend.
5. Check the 7-day and 30-day panels of the models you use (from /models) and the incident list on https://router.one/status.
6. If it fits, top up for real usage or pick a plan; for a limit raise or an annual contract, use the business contact below.

Business contact

Email support@router.one and start the subject with [Business]:

• [Business] Annual contract: your account ID, expected monthly spend and use case, and the term you need.
• [Business] Higher rate limits: your account ID, the key name (never the key itself), and your expected peak requests and tokens per minute.
• [Business] Building on Router One: your account ID, expected monthly spend, and what you are building for whom.

FAQ