Account management
Keys, balance, and what happens when the wallet reaches zero.
How does billing work?
Prepaid wallet. You top up, calls draw down the balance, and there is no monthly fee and no per-seat charge. Only successful requests are billed — failures and timeouts cost nothing.
What happens when the balance hits zero?
Calls return HTTP 422 with
BILLING_INSUFFICIENT_CREDITS. Nothing is deleted, no key is
revoked, and topping up restores service immediately. This is a balance signal, not an error in your request.
Can I get unused balance back?
Unused balance can be refunded on request. Consumed usage cannot, since it was already paid to the upstream provider. Refunds are settled across your whole account, and bonus credit you received earlier is clawed back — see the Refund Policy.
How many keys should I create?
One per independent consumer — per app, per environment, per team. Spend is tracked per key, so separate keys are what make per-team accounting possible after the fact. Sharing one key across everything is convenient until you need to answer "which project spent this".
What do keys look like?
New keys use the sk- prefix. Keys issued before the change use rmx_live_ and continue to
work — there is no migration deadline and no behavioural difference.
Can I see what a key spent?
Yes. Per-key spend and per-request usage are in the console under usage and logs. Each request records the model, token counts, and the amount charged.
To read balance and spend from code instead, call GET /v1/key/info or
GET /v1/account/info with the key — see Balance & spend API.