Credits
The wallet, holds and captures, operation pricing.
One wallet, one balance, shared by every Solved product on your account. 1 credit = 1 ₽. Paid calls debit
it; the price per operation is published per product (see each product's pricing page) and keyed as
<product>.<family>.<method>, e.g. link.api.link_create.
How charging works, end to end:
- Before your call runs, we place a hold for its worst-case price (relevant for calls with a price that depends on input, e.g. a bulk export).
- If the call succeeds, we capture the actual price — never more than the hold.
- If it fails for any reason, the hold releases automatically. You are never charged for a failed call.
A call that would take your balance below zero is rejected up front with 402 insufficient_credits and
never runs — so you can't end up in a state where a failed charge still did the work.
Paid responses — REST and MCP alike — include credits_charged (or credits_reserved + a job_id for
async operations, with the real charge appearing on the finished job) and credits_balance, so you always
know the cost and what's left without a separate call. For a balance check that costs nothing, call
solved_get_credit_balance (MCP) or read it off any other paid response.
Next: Account and credits · Errors