How it works

The request path

1. You send a request to one base URL with your sk_ key.
2. Roteo routes it. The gateway sits in front of multiple model providers and picks an efficient path. Where an eligible alternative is available, it may retry or reroute a failed request; failover depends on model availability, request type and limits, and is not guaranteed.
3. The model runs and its output comes back to you.
4. You pay for that request. The cost settles onchain from your own wallet over x402, capped by your balance. You only hold stablecoins; Roteo covers the network gas.

Where the inference comes from

Every request is served by the same frontier models you would reach going direct. Roteo may source inference capacity at volume-based provider rates and aims to price requests competitively, and onchain settlement leaves out card processors and subscription margins. Listed prices may change by model, provider and network conditions.

What Roteo never does

• Store your content. Prompts and responses are never kept, and the web chat stays in your browser. See Privacy.
• Hold your funds. Your wallet is self-custodied and only you control it. See Pay-per-call billing.
• Rewrite the output. Model-generated content is never editorially rewritten. Unsupported request parameters may be normalized before inference, and the OpenAI-compatible endpoints translate the response format; provider-specific processing and API behavior still apply.