Documentation
Spin up a gateway your customers call as a base URL, name the models they see, decide how those names resolve, mint a key per end user, and metering holds all the way through.
Get started
Welcome
The portal for your AI product: gateway, routing, metering, and spend control.
Introduction
The shape of the system, and where your code touches it.
Quickstart
Mint a key for one end user and make a real call through your gateway.
Authentication
Two kinds of key, pointed at two different things, and never interchangeable.
Core concepts
Applications
The container everything else belongs to, and the two hostnames it gets.
Keys and end users
One key per end user, and why never a header.
Wallets and holds
Where the money sits, and what a hold actually is.
The ledger
Append-only, and why that is not negotiable.
Bundles
Which models a key may reach, and at what markup.
Pricing strategies
How you charge end users maps onto wallets, plans, markup, and job ceilings.
Subscriptions and overage
What a paid bundle mints each period, and what happens when it runs out.
Credit systems
Name your own credits, decide when they mint, and let the gateway spend them down.
Spend caps
A hold before dispatch, and a stream that stops.
Outcomes
Budget a unit of work, not a request, when one job is several calls.
Model aliases
Your names for models, not the provider's.
Routers
A named policy over your model names, when one source is not enough.
Provider accounts
Your provider accounts, what we do with them, and the catalog they draw from.
Bring your own key
Your provider account, sealed with KMS.
Emitters
Settled usage, delivered where you bill from.
Integrations
SDKs
Surfaces
The gateway
Your gateway host: four wire formats, model resolution, and the only path that moves money.
Calling the gateway
OpenAI, Anthropic, Gemini, and curl: non-streaming, streaming, and cross-protocol.
The portal
Where your customers see their own usage, spend and keys.
The console
Where your team runs the account.
Examples
Metered chatbot
A chat product where every customer has their own balance and their own ceiling.
Usage-based pricing
Charge for what they call: your markup on the wire, their wallet on the meter.
Outcome-based pricing
Sell a finished job. Budget the run. Meter every call that belongs to it.
Design a credit system
Welcome credit, sellable packs, and a monthly allotment, one product, end to end.
Per-seat agents
One customer, many agents, and a budget that does not let one of them eat the month.
Prepaid credits
Sell a balance up front, take your margin at the top-up, and let the meter run it down.
Reselling with markup
Your own provider account on the path, your own price on the invoice.
Reference
API reference
The OpenAPI document is the list, generated from the routes that are served.
Every operation
The command and the route that reach each operation.
Usage and margin
What was called, what it cost you, and what was left over.
The request log
One row per call, why it cost what it cost, and what is deliberately absent.
Errors
Stable codes, and what each one means.
Lossy protocol conversions
What is not preserved when inbound and outbound wires differ.
FAQ
The questions that come up first.
Changelog
What shipped, newest first.