Service terms.
The current operating boundaries for evaluating router.
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.
Commercial questions
Use enterprise inquiries for proposed terms or operating requirements. See privacy information for data requests.