Balance and usage
How much you have used, and how tryVidimus counts it.
How the balance works
Your account holds a balance in euros. Sealing one proof in production debits it at the current price (see the pricing page); everything else is free. The API fields keep their historical names (balance, granted, consumed, credits_consumed): their amounts are in euros.
The sandbox is free
Proofs sealed with a sandbox key (sk_test_…) never debit your balance. The balance belongs to your account: a sandbox key shows the same balance as a production key.
When the balance is debited
At the moment the proof is sealed, not when the capture session is created. Until then, credits_consumed is 0 on the proof.
When the balance reaches zero
Today nothing is blocked: the balance can go below zero and stays visible.
Read your balance
balance is what is left, in euros: everything added minus everything debited.
$ curl https://api.tryvidimus.com/v1/credits \ -H "Authorization: Bearer $TRYVIDIMUS_API_KEY" { "balance": 940, "granted": 1000, "consumed": 60 }
List the movements
Each movement is either a grant (funds added) or a consumption (a debit, with the proof that caused it). Amounts are in euros. Use the cursor to read the next pages.
$ curl "https://api.tryvidimus.com/v1/credits/transactions?type=consumption&limit=20" \ -H "Authorization: Bearer $TRYVIDIMUS_API_KEY" { "data": [ { "id": "cre_01m4akapdbe8e8qq3er9r5qwyj", "type": "consumption", "amount": -1, "reason": "proof_sealed", "proof_id": "prf_01m4akapdbe8e8qq3er9r5qwyj", "created_at": "2026-10-08T10:00:00.000Z" } ], "has_more": false, "next_cursor": null }
What one proof debited
GET /v1/proofs/{id} returns credits_consumed, the amount debited in euros. The same movement appears in the list above, with the identifier of the proof.
These routes need a key with the read_proof scope.