Get started
Welcome
The portal for your AI product: gateway, routing, metering, and spend control.
Seams sits between your product and the model providers. Your customers call your gateway under names you choose. Bundles decide what they can reach, routers decide how those names resolve, and every request is metered against a balance with a cap that holds for the life of the stream. They get a usage page with your name on it.
Point your OpenAI, Anthropic, or Gemini client at your application gateway, mint one ak_ key per end user, and metering happens on the request path.
Start here
Introduction
What sits where, and which problem each piece solves.
Quickstart
Mint a key and make a real call through your gateway.
Calling the gateway
OpenAI, Anthropic, Gemini, and curl: including streaming and cross-protocol.
Core concepts
Balances, holds, aliases, and caps: the words used across these guides.
Credit systems
Design packs, plan allotments, and what one credit means in your product.
Pricing strategies
Usage-based, prepaid, plans, outcomes: which nouns to use.
Outcomes
Budget a job, not a request, when one unit of work is several calls.
Examples
Full integrations you can read end to end and adapt.
What it replaces
| You would otherwise write | What Seams does |
|---|---|
| A proxy and a redeploy every time a model SKU changes | Aliases and routers you change in the console |
| A per-user token counter and a cron to reconcile it | Usage recorded per request, per key, per model |
| A balance column and a race you hope never happens | available = balance − hold, atomic |
| A cap check before the call that is wrong mid-stream | A reservation that stops the stream at the limit |
| Provider keys in your env, shared by everyone | One credential per customer, decrypted per request |
| A billing page you keep meaning to build | A branded portal on your subdomain |
Seams never stores prompts or completions. The usage record has no place for message content. That is by design, not a setting.