HTTP 402 · USDC · Arc

Private agent payments on Arc

Pay for APIs, data, and compute over HTTP 402. Merchants settle in USDC on Arc. Your funding wallet and purchase graph stay off the public ledger.

x402 traceRequest

GET /api/market-data

Authorization: Bearer agent_…

Tap a step or replay the private payment loop.

Same 402 interface, private settlement

Scroll the trace. Each card stacks horizontally as the path advances.

step 1/4402

HTTP/1.1 402 Payment Required
X-Payment-Amount: 0.05
X-Payment-Currency: USDC
X-Payment-Network: arc

The resource responds with amount, recipient, and network on Arc.

HTTP 402 carries the public payment terms. The agent never pays from its funding wallet directly.

step 2/4POL

agent.policy.check()
allowlist: PASS
daily_budget: PASS
route: z402/private

Spend limits, allowlists, and budgets run on the agent before any payment.

Policies stay on the agent. Merchants never see your caps, allowlists, or strategy.

step 3/4Z4

z402.route(
  from: agent_vault…c91d
  to: gateway.z402…8f2a
  visibility: merchant_blind
)

z402 routes the payment so the merchant never sees your funding wallet.

Gateway or stealth routes break the link between your treasury and the purchase graph.

step 4/4200

HTTP/1.1 200 OK
X-Payment-Receipt: arc:0x…a91
Settled: 0.05 USDC
Merchant view: gateway only

The gateway confirms and settles the public leg. The agent retries with a receipt.

Arc finality in under a second. Merchant gets USDC; you get the resource and a local receipt.

Same wire. Two observers. Redaction is the UI.

Arc ships x402, USDC-native gas, sub-second finality, and facilitator infrastructure. z402 adds privacy on those rails instead of replacing them.