Credits & Billing
How balances, micro-USDC units, and overdraft protection work.
The gateway is credit-based: you fund a balance, and each inference request is billed against it.
Balance units (micro-USDC)
All balances are stored as micro-USDC — integers with 6 decimal places.
| Value | Unit | Convert to USD |
|---|---|---|
balance_usdc | micro-USDC | / 1_000_000 |
available_usdc | micro-USDC | balance_usdc − locked_usdc |
total_charged_usdc | micro-USDC | / 1_000_000 |
So 5_000_000 micro-USDC = $5.00.
Pricing
Prices reported by GET /v1/models are the prices you're charged — the published rate is the rate billed, for both prompt and completion tokens. This holds for the bare model IDs shown in the catalog; a provider-prefixed ID (e.g. <provider>/claude-haiku-4-5-20251001) instead bills at that upstream's real rate. See Pricing.
A model offered at several context windows is listed once per window, under a context-suffixed ID — hypothetically, some-model-200k and some-model-1m for a model offered at both 200k and 1M tokens — each window is priced and billed separately.
Overdraft protection
Balance is reserved before the upstream call starts. The reservation covers the maximum possible cost (based on max_tokens), and the actual charge is always ≤ that estimate.
This guarantees concurrent requests can never overspend your credit. If the balance can't cover the estimate, the request is rejected with HTTP 402 before any provider call.
Checking usage
Query GET /v1/usage/:wallet for balance plus per-key request counts, token totals, and charges. See the Usage endpoint.