Routes with a clear plan.
Match models and native protocols, then use priorities and weights. Failover respects the response boundary.
A GATEWAY FOR BUILDERS
Your models.
Your next idea.
Explore models, use a familiar protocol, and follow the usage and cost of each request. A clear starting point for what you build next.
Read the quickstartSTART WITH A REQUESTJSON / SSE
◇
Models are being prepared
START WITH A MODEL
Different models. Different strengths.
Compare enabled capabilities and current platform rates.
A record you can follow.
Follow usage and charges with one platform request ID. Request and response bodies are not stored; model calls return live JSON or SSE.
Know what makes the cost.
Separate input and output rates, request-time snapshots, and daily charges you can inspect.
Your next idea starts here.
Four native text protocols with one balance and billing history.