For model consumers
A catalog of every model available to you: where each one is hosted, what each endpoint costs, and which ones your team is cleared to use.
- Where each model is hosted
- What each endpoint costs
- What your team can use
A unified access layer for LLMs. Apps and agents from any vendor call commercial and open-weight models through one endpoint, routed by cost or fit and metered per team, while provider keys stay in the gateway.
Who calls it
AI Gateway
Every request, in this order:
Commercial models
Open-weight models
Hosts
Commercial models and open-weight models such as Llama and Qwen sit behind a single endpoint. Switching models means changing a model name, not an integration.
Every request is metered in tokens and cost, then attributed to the model, the team and the consumer that made it, so spend can be billed back to whoever used it.
Cap spend and requests per team, project or app key, and choose which models each team is cleared to use.
Get an alert at 80% of a budget. At the cap, the gateway throttles, blocks, or falls back to a cheaper model, whichever you chose.
Mask personal data and stop prompt injection before a request reaches a model.
Who sent it, with which key, to which model, how long it took and what it cost.
Set a routing rule per model or per consumer: lowest cost, a preferred host, or one fixed endpoint. If an endpoint is down or rate limited, the request falls back to the next one.
Spread traffic for one model across hosts, regions and keys, so no single one becomes the bottleneck.
Simple requests go to a cheaper model and hard ones to a stronger model, without a code change.
Answer repeated and near-identical requests from a cache instead of paying a model for them again.
A catalog of every model available to you: where each one is hosted, what each endpoint costs, and which ones your team is cleared to use.
Data centers and AI factories onboard and host models, set their own pricing, and track usage and revenue per model.