Skip to content

Agent payments

Pay per request with a signed USDC transfer. Attribution is a separate reputation signal.

Direct x402 is runtime-configured, with testnet as the default network. The parking vault is testnet and earns no yield; the mainnet attribution ledger is fundless.

01
Request a resource
An enabled seller responds with HTTP 402 and payment requirements.
02
Sign & retry
The agent signs an EIP-3009 authorization and retries with PAYMENT-SIGNATURE.
03
Verify & transfer
The direct facilitator verifies it; settlement sends USDC from payer to seller.

The active facilitator in lib/x402/config.ts is selected with X402_SETTLE_PROVIDER=direct. Supported networks and the seller destination are configured at runtime. When unconfigured, the score seller returns HTTP 503. Do not infer a live mainnet payment service merely from the source supporting that network.

/api/x402/score?address=<wallet> is the paywalled score endpoint. Its current handler verifies the authorization before serving the resource and initiates settlement asynchronously; a successful resource response is not itself proof that the payment transaction confirmed.

The separate AIAttribution ledger and ERC-8004 identity support agent reputation. Start at agent integrations; recorded contracts are in Contracts.

Source reference

Behavior above follows these files in the Mintware repository. Deployment records describe recorded state, not a fresh chain read.

  • lib/x402/config.ts
  • lib/x402/directFacilitator.ts
  • lib/x402/directSettler.ts
  • app/api/x402/score/route.ts
  • config/deployments.json
  • .claude/rules/agents.md