Kill false payment-chain claims: USDC settles on Base + Polygon only

[Deesmo]

What

x402 payments settle USDC on Base and Polygon only (verified against live 402s, 2026-07-31). The live surfaces claimed "9 chains", "9 networks", "15+ blockchains", and "USDC (Base, Ethereum, Solana + more)" — all false. This PR replaces every false payment-chain claim with honest copy. Copy/metadata only — zero payment-logic changes.

Changes (42 files, +112/-176)

Public HTML — homepage (badge wall, stat cards, JSON-LD FAQ, chain paragraph), preview-a/b/c/d/e + preview-landing, x402.html, x402-guide (incl. "Supported Chains" grid), faq, compare, developers, agents-landing, ai-agent/ai-media/web-data/utility/mcp-server/crypto-tools cards, for-providers, migrate-from-skyfire, migrate-from-rapidapi, changelog + changelog-tonight, blog.html, blog-x402, blog-x402-directory, blog-skyfire-migration.

Machine-readable surfaces

• llms.txt + llms-full.txt and the inline LLMS_TXT template in discovery.ts (x2 spots)
• /stats → supportedChains = ["Base", "Polygon"] (drives stats.html live)
• /trial → supported_networks: ["Base", "Polygon"]
• .well-known/agent.json (description + x402.networks), .well-known/ai-plugin.json
• x402-directory.json arch-tools entry: chains_supported → base+polygon, tokens_supported → USDC
• mcp/src/server-card.json ("crypto data (15+ chains)" kept — that's data coverage, true), sdk/python/README.md

Reactivation email (reactivationEmail.ts, goes to 217 people): "USDC (Base, Ethereum, Solana + more)" → "USDC (Base or Polygon)" in both text and html renders.

Deliberately NOT changed

• discovery.ts env-gated accepts[] builder, x402.ts/x402-sdk.ts middleware, facilitator.ts getSupportedNetworks(), x402V2 lib — payment logic per task scope.
• facilitator.html + the facilitator row in pricing.html: that's the separate facilitator product, whose own /supported endpoint (logic) returns 7 networks and whose page carries an explicit beta caveat ("Settlement is available on Base mainnet. Other networks are in verification-only mode"). Flagging for a follow-up ruling rather than silently rewriting a product spec.
• docs-x402-guide.html code samples ("Accept USDC on Base, Ethereum, Arbitrum") — provider-side protocol tutorial, not a claim about our rails.
• Crypto data tool descriptions (eth-price, solana price lookups, "crypto data 15+ chains") — true statements about data coverage.

Verification

• tsc --noEmit: no errors in any edited file (pre-existing stale-Prisma-client errors in untouched files only; CI's prisma generate && tsc regenerates)
• node tests/reactivation-render.test.mjs against a fresh build: all pass; rendered output proven to contain "USDC (Base or Polygon)" and zero Ethereum/Solana mentions
• node scripts/check-price-drift.mjs: OK (no pricing amounts touched)
• Repo-wide grep: zero remaining 9 chains|9 networks|9 blockchain|15+ blockchains|across 9 outside tracked dist (regenerates on deploy)
• Build churn reverted: git checkout -- api/dist api/node_modules before commit; staged exactly 42 source/public files

Do not merge — conductor merges after CI.

🤖 Generated with Claude Code

---

Note

Medium Risk
Wide marketing/API-metadata changes can mislead integrators if copy diverges from live 402 behavior, but risk is limited because payment logic is unchanged; residual inconsistency (e.g. some stat blocks still showing other chain counts) may remain outside the edited strings.

Overview
Aligns public and machine-readable messaging with actual x402 settlement: USDC on Base and Polygon only, replacing overstated claims about “9 chains/networks,” many EVM/Solana rails, and multi-token support (USDT, ETH, SOL, etc.).

Discovery & APIs: agent.json / ai-plugin.json, x402-directory.json, discovery.ts (LLMS_TXT + platform description), stats.ts (supportedChains), and trial.ts (supported_networks) now list base + polygon and USDC only.

Site & docs: Homepage, category pages, x402 guides, FAQ, compare, migration blogs, changelogs, preview landings, embedded landing.html / landingHtml.ts, MCP server card, Python SDK README, and transactional emails (email.ts, reactivationEmail.ts) use consistent Base or Polygon / 2 networks wording and trimmed chain badge UI where applicable.

No payment middleware changes — facilitator logic, 402 accepts[] builders, and settlement code are untouched per scope.

^{Reviewed by Cursor Bugbot for commit 0091635. Configure here.}

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue.}

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 0091635. Configure here.}

[cursor]

Discovery description contradicts supportedRails

High Severity

The /.well-known/x402 JSON description now states USDC on Base or Polygon only, while supportedRails is still built from the env-gated multi-chain accepts list (Ethereum, Solana, USDT, native tokens, etc.). Same response body advertises two incompatible settlement stories.

 

^{Reviewed by Cursor Bugbot for commit 0091635. Configure here.}