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 downstream costs — what the gateway pays the provider — and you're billed at those rates. See Pricing.
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.