Two useful endpoints, one original Base USDC receiver
The free example is explicitly fictional, not on-chain proof. These products are hosted by the same single human owner's existing VM5 merchant and settle directly to that owner's original VM1 MetaMask public receiving address. This static page never processes payments, signs messages or receives API credentials.
The bounded X Layer case
| Data network | X Layer, chain ID 196 |
| Earlier pinned block | 73915245 |
| Later pinned block | 74009771 |
| Compared inputs | 20 fixed, publicly readable TapeOut CPU0/factory/market fields |
| Observed differences | factory.cpuCount and factory.implementation |
| Observed equal fields | 18 of 20 selected fields |
| Payment network | Base mainnet eip155:8453; native Circle USDC, 0x833589fCD6eDb6E08f4C7C32D4f71b54bdA02913 |
| Payment recipient | 0x4e3106520E40af30870caFE78da1B1e7110eD98E |
These are the original operator's read-only historical snapshots. “Later” means later than the selected earlier block, not the latest live block. A changed implementation is a reason to inspect source and governance, not evidence of a compromise. The comparison is neither a complete chain history nor an independent security audit.
For an x402 v2-compatible machine buyer
The original paid GET is open to an unpaid quote request. It responds with HTTP 402 and a PAYMENT-REQUIRED header. Your client, not this page, must verify the quote, ensure chain/token/recipient/amount are allowed, and follow its own payment limits before authorizing anything.
curl -i 'https://vm5-openapi-x402.onrender.com/v1/tapeout-cpu0-diff'
# HTTP 402 Payment Required; no wallet action by curl
# x402Version: 2; scheme: exact; network: eip155:8453
# amount: 10000 USDC atomic units (0.01 USDC)
# payTo: 0x4e3106520E40af30870caFE78da1B1e7110eD98E
Use a compatible, authorized x402 client for a real purchase. The quote and the listing are not themselves evidence of settlement or successful delivery. Never paste private keys, payment signatures, cookies, bearer tokens, raw HAR captures or customer transaction details into a web form.
Why this scope is intentionally narrow
What the report can say
For two explicit block heights, it can enumerate selected field changes and unchanged fields with source pins, return structured machine-readable JSON, and distinguish X Layer data from Base USDC payment metadata.
What it cannot say
It does not certify contract solvency, audit every intermediate block, inspect all assets, prove a vulnerability, forecast token prices, guarantee a current chain state, or guarantee a merchant payment will settle. Unavailable RPC should fail as unavailable rather than request money for broken data.
Implementation and verification trail
This is one commercial API offered by a transparently AI-assisted workflow for a single human beneficial owner, not a registered audit firm. The code was tested on local mocked-chain scenarios in the original merchant project, and the public upstream implementation is available for inspection. Static content is explanatory; only the live API produces a real paid response.
Merchant's public TapeOut source ↗ · Live OpenAPI ↗ · Free illustrative response ↗
Publication note, 24 October 2026: the 0.01 USDC two-block API has no verified independent paid purchase in the operator's inspected public settlement summaries. Its existing marketplace and directory submissions are visibility, not revenue. The old 0.005 USDC single-block API had earlier unrelated historical paid verifier calls, not a customer purchase from this page. No guaranteed sales or net earnings are claimed.