Guide
Credits & billing
How metering works, packs, refunds on failure.
Credits are the API's single unit: flat-priced per call, shared by every key on the account, bought as prepaid packs or dropped monthly by a plan. No token arithmetic — a completion on RP+ is 3 credits whether it renders 50 tokens or 800.
Top-ups
Packs are bought by card on the billing page. Larger packs carry bonus credits instead of a different rate, so per-call prices never change. Credits do not expire.
$10
1,000 credits
Try every model properly.
$25
2,750 credits
A real week of creating, bonus included.
$50
5,750 credits
Enough to ship a beta.
$100
12,000 credits
Production traffic, best rate.
What things cost
Cost calculator
A $10 Starter pack (1,000 cr) covers 333 completions of eroq RP+ chat. Prices are flat — no token math, no surprises.
Metering
A call charges before the engine runs, and refunds itself if the engine returns nothing — the refund appears as a negative row in your usage ledger. Every JSON response carries the meter:
"usage": { "credits_spent": 3, "credits_remaining": 997 } Binary responses (speech) carry the same numbers in X-Credits-Spent / X-Credits-Remaining headers. Poll GET /v1/account for the balance.
Running out
A call that costs more than your balance fails fast with HTTP 402 and charges nothing — see Errors for the handling pattern worth building on day one.
To keep a pipeline from stopping at zero, the workspace owner can turn on auto top-up on the billing page: when the balance falls below a threshold (200, 500, 1,000 or 2,500 credits), the pack they picked is bought on the saved card, up to a monthly limit they set.