BASE RECEIPT · FOR AGENTS

Payment intent. Verified receipt.

Prepare a Base USDC payment request through MCP, submit it with your own wallet, and turn the confirmed transfer into a server-verified receipt.

Connect your agent

Streamable HTTP endpoint:

https://base-receipt-six.vercel.app/mcp

The endpoint accepts MCP requests over HTTP POST. No Base Receipt API key is required.

View machine-readable capabilities ↗

Run a live MCP self-transfer check ↗

Two tools, one receipt flow

  1. prepare_base_payment accepts a decimal USDC amount and recipient. It returns a signed order valid for 15 minutes, an order token, and unsigned transaction data with Builder Code bc_87fjmj1l.
  2. Your wallet reviews and submits the returned direct USDC transfer on Base Mainnet, chain ID 8453. Preserve the returned calldata, including its attribution suffix.
  3. issue_base_receipt accepts the transaction hash as paymentId and the original orderToken. It verifies settlement and persists the receipt claim.

Preparation example:

{"amount":"0.01","recipient":"0xYourRecipientAddress"}

Replace the placeholder with the intended recipient. The service prepares transaction data; wallet approval and payment submission stay with the caller.

What the receipt proves

The server checks a successful direct USDC transfer, the exact amount and recipient, the sender and Base Receipt attribution. A payment already claimed by another order is rejected.

Use the same signed order when retrying within its validity window. The current verifier supports direct wallet transfers; smart-account and batched payment flows are not supported.

Preparing an order does not establish payment or product adoption. A receipt proves the checked transfer, not delivery of goods or services.

Open the wallet payment page

Source and integration documentation ↗

Base Agent Meter: inspect x402 APIs and existing settlements ↗