Test the endpoint and send your first requests.
- OpenAI-compatible /v1 endpoint
- Access to the core model routes
- Usage and quota visibility
- Best for prototypes and evaluation
Pricing
Simple usage-based access for teams testing multiple models.
Start with a single key and transparent usage. Upgrade only when you need higher volume, custom routing, or dedicated support.
Run production workloads with cleaner routing and quota control.
- Default, premium, and fallback routes
- Higher usage limits and broader catalog access
- Better fit for customer-facing products
- Priority fixes for routing issues
Handle larger volume, stricter controls, or custom rollout needs.
- Custom model routing and provider policy
- Operator support for launch and incidents
- Useful when the API becomes business-critical
- Volume pricing by request pattern
What changes between plans
Same API surface. More control as usage grows.
Customers keep the same endpoint while you add better routing, limits, support, and observability behind the scenes.
More routing control
Move from a basic working setup into clearer separation between default, premium, and fallback traffic.
More operator clarity
Use one workspace for logs, channels, keys, and policy while your internals evolve.
More rollout flexibility
Expand the model mix or adjust upstream logic without forcing customers to rewrite their clients.
Next step
Request a key and test the model routes.
Early access keeps setup manual while billing and public signup are finalized.