Test wallet

Give agents fake USD test balance, spending limits and human approval for test payments.

Loading test payments…

About Test wallet

Give agents fake USD balance and spending controls. Test mode only, with no real funds, blockchain transactions or private keys.

When to use it

Test an agent payment and human approval with fake money.

Test wallet example

create_test_wallet({name: "Research agent", balance: 100}) → create_test_paywall({name: "Article", amount: 1}) → wallet_pay({id: wallet.id, payee: paywall.endpointUrl, idempotencyKey: "article-1"}) → inspect the ledger

How to use it

Create a test wallet and a paywall or checkout.
Call wallet_pay with a payee and idempotencyKey. Above the threshold, share the approval link with a human owner or admin.
Resume with the same key, then inspect the ledger. Add free test balance when needed.

Test an agent that pays

Create a wallet with fake USD balance, then a paywall that returns HTTP 402. The agent calls wallet_pay with the paywall URL. A payment within its controls unlocks the content; an amount above the approval threshold asks a human before it can debit. Repeating the same idempotency key resumes that payment safely.

Only a signed-in workspace owner or admin can change wallet limits and approval thresholds or answer approvals. API keys can read controls, add free test balance and request payments. Every test wallet, paywall and checkout counts toward the normal resource pool and expires under mock retention rules.

No real payment details

These resources use fake test money only. No blockchain settlement, real funds or private keys exist. The public checkout offers test outcome buttons and a second confirmation step. It never collects card details. API and MCP clients may submit fake fixtures from the card generators; the service retains only the result and last four digits.

Checkout events are generic, signed and timestamped. Save the webhook secret returned once, verify the signature on raw bytes, reject stale timestamps and deduplicate event IDs. Inspect attempts and delivery results inside the dashboard or through the API.

Limits & privacy

Counts toward normal resource and storage limits. Only owner/admin browser sessions can set limits and approval thresholds, including on creation. Keys receive plan defaults. Payments are limited to 60 per workspace per minute. Top-ups are free and rate-limited by plan. Balance and amounts are capped at 1,000,000 test units. Daily limits use UTC. Approvals belong to one caller and payment. Authorized paywall tokens reserve balance for up to five minutes and cannot be replayed.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.