Test x402 paywall

Test HTTP 402 payment flows with wallet tokens or permissive fixtures. No real settlement.

Loading test payments…

About Test x402 paywall

Test HTTP 402 payment handling against a public x402 v1 endpoint. Test mode only: no settlement or blockchain calls.

When to use it

Test an agent payment and human approval with fake money.

Test x402 paywall 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

Set a test price, payment modes and JSON response.
Request the URL to receive payment requirements. Use wallet_pay or retry with its returned X-PAYMENT header.
Inspect calls and refusal reasons. Use permissive mode only for testing x402 payload structure.

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

Uses normal mock resource retention, storage and resource allowances. Wallet tokens are HMAC-protected, URL-bound and single-use. Permissive mode validates v1 exact/base-sepolia structure only, without signature verification or replay protection for fixtures. Success returns X-PAYMENT-RESPONSE. Responses are up to 16 KiB. Configuration and history require workspace access.

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