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. Direct API clients can explicitly fund Wallet Credits
with /v2/wallet/topup; MCP clients can read balances and existing funding
status, while funding starts on the website. 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/prepare | Prepare saved-card funding without charging. Returns the issued operation and exact confirmation for fresh approval. Requires a stable `Idempotency-Key`. |
| POST | /v2/wallet/topup | Explicitly fund by saved card or invoice. New saved-card funding requires the prepared `funding_operation_id`, exact returned confirmation and stable funding `Idempotency-Key`. |
Headless top-up guardrails
Saved-card top-ups through the direct API charge the authenticated account's
default saved card only after explicit approval for the chosen amount.
Prepare first without charging, show the returned exact confirmation for
approval, then fund using that issued operation. Clients retain the
original arguments and keys across reloads; an unknown outcome must
recover the original request without preparing replacement funding.
Top-ups are bounded by the account's saved-card funding limit. Invoice
top-ups can be larger, but Wallet Credits become available only after
payment is received, matched to the invoice and confirmed. 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.
In billing, choose Pay later, enter an amount in $500 increments, and
provide the purchasing institution or person's billing details. The
purchaser can differ from your signed-in Om account; the credits always
belong to the Om account that requested the invoice.
Direct API callers use payment_mode: pay_invoice and invoice_buyer.
Required buyer fields are name, email, address_line1, city,
postal_code and the two-letter uppercase country. Optional fields
are address_line2, state, contact and department. For a $500
invoice, use amount_cents: 50000 and obtain explicit approval for
I approve creating a $500.00 Wallet Credits invoice. before submitting.
Om and Zentools MCPs do not expose invoice creation or saved-card
funding tools. Direct API clients retain the original request and
idempotency key to recover the same invoice after an interrupted response.
Open the individual invoice link returned by the request. The invoice
identifies the purchaser in its memo and contains payment instructions.
Include its invoice number with the payment so it can be matched. A
purchase order is optional for creating the invoice; your institution
may require one for its own procurement process. Creating an invoice or
supplying a PO does not add credits. Check billing history and your
Wallet balance after payment is confirmed.
Use /v2/pricing to review current API pricing and /v2/credits to
confirm available Wallet Credits before large jobs.