Credits & pricing

What uses a credit?

Choose any whole quantity from 10 to 100,000 credits. The workspace shows the current USDC price per credit and exact total before checkout.

All API keys in your workspace share one credit balance. Cancelling an invoice does not return its creation credit. The purchase selector starts at approximately 5 USDC; presets offer 5, 20 and 50 USDC. A 10-credit trial remains available but may not cover the success-fee reserve. Up to two unpaid package checkouts can be active; requesting the same quantity and price reuses the active checkout. New purchases/request bindings are limited to 10 per day. Credits are service units, not a withdrawable USDC balance. Package purchases do not authorize automatic wallet debits.

Network transaction fees are separate from invoice credits. Review the network and any fee shown by your wallet before confirming payment.

Success fee and reserved credits

The current success fee is 0.2% of a confirmed hosted workspace payment, including standalone PaymentIntents. It is additional to creation credits. The seller receives the entire USDC payment in their wallet; this fee is paid from their prepaid service credits. Credits are internal service units, not a blockchain token or a withdrawable deposit.

Creation atomically spends 1 / 2 / 3 credits and reserves the success fee. Available balance excludes all outstanding reserves. Insufficient available credits returns HTTP 402 without creating a payable invoice or spending credits. Each simultaneous invoice needs its own reserve. Successful payment consumes that reserve exactly once. Unpaid cancellation or expiry releases it; pending verification or manual review keeps it reserved until resolved. Expiry release may wait for the server maintenance pass. Cancellation never refunds the creation charge.

For example, at 0.2% and 0.01 USDC per credit, a 100 USDC invoice reserves 20 credits. A one-hour invoice therefore needs 21 available credits: 1 spent immediately, 20 reserved. Ten such unpaid invoices need 210 credits initially, with 200 held in reserve. The example rates are illustrative; the live tariff and creation form show your actual terms.

The fee is calculated from the invoice amount, rounded up to 0.000001 USDC, then converted at the credit price recorded at creation and rounded up to 0.000001 credit. There is no rounding up to a whole credit. Rate changes affect new payment windows only; renewal reserves at the current rate. Invoices issued before this fee was introduced retain their original terms. Credit-package purchases are exempt. No automatic refund of an already charged success fee is provided for a later seller refund.

GET /billing exposes exact decimal strings availableCredits and reservedFeeCredits, plus successFee.basisPoints and successFee.creditPriceUSDC. Use these exact decimal fields rather than the whole-credit convenience field. Invoice and PaymentIntent responses include their frozen successFee terms, credit amount and status: reserved, charged, released or waived. Receipts retain the charged fee. Do not treat a local quote as a reservation; only successful creation reserves credits.

Estimated network costs

The workspace displays cached reference estimates, with the cheapest complete estimates first. These are not final transaction quotes. Network fees may be paid in the network’s native token. While the workspace Reports tab is visible, estimates refresh automatically every two minutes; hidden tabs pause refreshes. The server supplies cached estimates rather than requesting blockchain data for each browser refresh.

Balance forecast

The Create button shows the payment window and total credits required now: creation charge plus success-fee reserve. Creation is charged immediately and is not refunded. Only the success-fee portion stays reserved. Confirmed payment consumes that reserve; unpaid cancellation or expiry releases it. A payment still being verified or reviewed keeps its reserve until resolved, even if its original payment window has elapsed.

The form forecasts the remaining available balance and the number of identical invoices you can open together. It uses the currently loaded balance, so other API activity can change the result. Server-side creation checks and reserves credits atomically. Refresh the workspace to retrieve a newer balance.

Agents can call GET {API_BASE}/billing/quote?amount=100&expiresIn=3600 with billing:read. The response includes creationCredits, reservedFeeCredits, requiredCredits, remainingCredits, shortfallCredits and affordableInvoices as exact decimal strings, plus sufficient. This free, read-only estimate does not reserve credits or guarantee a later creation will succeed. A concurrent request or tariff change may change the actual terms.

Credit activity and reconciliation

Open Purchases → Credit activity for purchases, creation charges, reservations, releases, success fees and branding charges. Entries include balances after the operation and invoice links when applicable. GET {API_BASE}/billing/ledger requires billing:read, returns 50 rows and a next cursor; pass it as before for the next page. The latest 2,000 movements are retained; export what you need to keep. Tracking begins with this feature and does not invent historical entries.

The visible balance refreshes about every 30 seconds and when returning to the page. Hidden tabs pause balance polling; failures use a longer retry interval. The forecast is still an estimate until the server accepts creation. Background reconciliation compares fee reservations with payment records in small batches. A mismatch requests operator review; it never triggers an automatic charge, refund or release.