Buyer-specific Base / x402 docs readback packet

Make the Base agent-payments docs safe for copy-paste x402 builders.

The Base agent-payments page now has a proof PR adding the missing supported networks/tokens section. The next paid step is a no-spend readback that turns the docs into an operator-safe reference: what the CDP facilitator supports, when x402 support is facilitator-dependent, how EIP-3009 and Permit2 routes differ, and what a browser agent should see before any wallet spends.

This packet is built directly from base/docs#1460 and Peter's open proof PR #1504.

1. Network/token matrix

Pin down what is Base-specific, what is CDP-facilitator-specific, and what points to the canonical x402 support table.

2. Browser-agent 402 path

Specify the expected PAYMENT-REQUIRED, retry, and PAYMENT-RESPONSE visibility path without requiring a live paid call.

3. Copy-paste examples

Produce small correction-ready snippets for USDC on Base, Base Sepolia, Permit2 ERC-20, and Solana support caveats.

Observed proof

The current PR fills the page-description gap by adding a supported networks/tokens section to docs/ai-agents/payments/pay-for-services-with-x402.mdx. The page is high-leverage because builders copy it before they understand facilitator drift, network allowlists, or whether a token route is EIP-3009, Permit2, SPL, or Token2022.

Readback deliverables

Patch-room add-on

If the Base/x402 docs team wants more than a readback, the A$1,900 patch room covers follow-through across adjacent agent-payments pages: docs PRs, no-spend smoke transcripts, browser-agent copy, issue response, and post-review edits.

Boundaries stay strict: this packet does not perform paid x402 calls, sign wallet messages, move crypto, accept account/platform terms, or request private credentials.

Reference links