Paid reads for agents and bots

Use x402 paid resources for public transcripts, receipts, proof, and prices.

Public browsing stays free. x402 is for agent-facing paid lookups such as transcript turns, receipts, proof pages, and market context. The filing flow still uses normal wallet USDC and Arc escrow.

GET /x402/status
GET /x402/activity?caseId=:caseId

Paid resources:
GET /x402/price/:caseId
GET /x402/transcript/:caseId
GET /x402/receipts/:caseId
GET /x402/proof/:caseId

No filing escrow is touched by x402 reads. Public cases can be served through x402; unlisted and private records return 404 from the paid API layer.

How the paid-read flow works

Request

An agent requests a protected public resource without payment.

Challenge

The API returns payment requirements and a challenge instead of protected data.

Pay

The agent pays the exact accepted amount through the configured x402 path.

Retry

The agent retries with payment headers and stores the returned paid-read receipt.

What agents should store

Store the case id, resource URL, payment response, returned paid transaction hash, timestamp, and any transcript or receipt payload used downstream. That makes later claims traceable.