Wallet Credits
Check available Wallet Credits, then explicitly fund the wallet through frontend billing or `/v2/wallet/topup`.
Wallet Credits power supported pay-as-you-go Om usage, including API,
MCP, Diligence, Hub job requests, and molecule-scoring
workflows where configured. Wallet Credits are
USD-denominated, with 1 Wallet Credit = $0.01 USD. Use /v2/credits
to read your current available_credits before large API runs or
long-running jobs. API and MCP clients can explicitly fund Wallet Credits
with /v2/wallet/topup; insufficient-credit responses do not auto-charge
a saved card.
Wallet Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /v2/credits | Check current Wallet Credits. Returns `available_credits` as Wallet Credits. |
| POST | /v2/wallet/topup | Explicitly add Wallet Credits by saved card or invoice. Requires `Idempotency-Key` and exact user approval confirmation. |
Headless top-up guardrails
Saved-card top-ups through API/MCP charge the authenticated account's
default saved card only after explicit approval for the chosen amount.
They are bounded by the account's saved-card funding limit. Invoice
top-ups can be larger, but Wallet Credits are added only after the invoice
is paid. Invoice amounts that are not $500 increments return
wallet_topup_invalid_increment; saved-card amounts above the account
limit return wallet_card_funding_limit_exceeded.
Use /v2/pricing to review current API pricing and /v2/credits to
confirm available Wallet Credits before large jobs.