Guide

Credits & billing

How metering works, packs, refunds on failure.

view as markdown

Credits are the API's single unit: prepaid, flat-priced per call, shared by every key on the account. No subscription and 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.

Starter

$10

1,000 credits

Try every model properly.

Builder+10%

$50

5,500 credits

Enough to ship a beta.

Scale+20%

$100

12,000 credits

Production traffic, best rate.

What things cost

Cost calculator

completions × 3 cr
300 credits$3.00 at Starter · $2.50 at Scale rate

A $10 Starter pack (1,000 cr) covers 333 completions of 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

HTTP 402

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.