router
ModelsSell capacity
More
DocsPricing historyModel rankingsA/B testingTechniquesIntegrations
Log inStart saving
router/Legal

Service terms.

The current operating boundaries for evaluating router.

Early access · Final commercial terms, the contracting entity, and jurisdiction have not yet been published. This page does not create an uptime commitment or a custom commercial agreement.

Access and credentials

Use an authorized account and keep your API keys confidential. A key grants access to the associated account’s balance and inference usage. Revoke any key that may have been exposed.

Requests and model availability

The service accepts the documented protocols and selects eligible providers automatically. Model versions, capabilities, limits, and capacity can differ by route. Unsupported features can return an error. The API reference describes the enabled endpoints and routing controls.

Prices and usage

Charges depend on the provider route that completes the request and the reported billable token usage. Input, output, cache reads, and cache writes can have different rates. Catalog prices are unit prices, not a total request quote.

A minimum discount requirement is enforced only against a verified reference price. A request can fail if no route meets its constraints. A settled billing record is the source of the final charge; failed attempts do not create a settled customer charge.

Evaluation and reliability

Review model output for your use case. Public health indicators report observations and do not constitute an SLA. Supplier coverage, contractual retention, and other enterprise requirements need separate review before relying on them.

Accounts and funding

Available funding methods are shown in the account interface. Where external payment processing is not configured, no card payment is collected. A supplier application or enterprise inquiry does not establish payment, payout, or reserved-capacity terms.

When offered, the first successful funding of at least $5 can receive $10 in promotional credit after verification, once per account and eligible card. Digital wallets are excluded. Paid credit is recorded separately while bonus eligibility is pending. Existing payments do not receive a retroactive bonus.

A successful refund or dispute withdrawal removes the associated bonus and adjusts paid credit, up to the original payment. Failed refunds or reinstated funds restore the corresponding credit. A reversal can leave a spent balance negative and pause automatic recharge. Further usage requires sufficient available credit.

Commercial questions

Use enterprise inquiries for proposed terms or operating requirements. See privacy information for data requests.

PrivacyTermsData protectionSubprocessors
router

Marketplace prices,
clear usage billing.

r→

Product

Models & pricingHow it worksTechniquesExperimentsSell capacity

Developers

DocsApp integrationsAPI reference

Company

EnterpriseLive marketsPricing historyStatus

Legal

PrivacyTermsData protectionSubprocessors
© 2026 routerOne API. More possibilities.