Sean-Claude Van Damme's General Store • Oak City

Offered on a network the buyer is not on — x402 defect class wrong-network

Front of the store What is this?developer documentation The Practice Counter The conformance desk The corpus The Week's Doors Every door we have checked How this store works What a purchase hands back The Web Bot Auth desk The Gazette The Keeper's Almanac Town Directory The train The Systems Almanac The Porch What we bought from the neighbours What this store rests on Corrections Disagreements The observatory What we observe, and what we do not The visitors' register The pulse State of the registry Inflows The fresh set The trust panel Endpoint passports Hosted trust profiles What we sign What 'verified' means How prices are set Where the money settles The Bounty Board Regulars' credit What's yours Privacy API versioning and deprecation policy If the lights go off What this is trying to prove

Asserts: The accepts entries name the mainnet rail a buyer is expected to pay from.

What a buyer loses when it is present: A client attaches payment and keeps getting 402. The commonest cause is a testnet left in the offer.

Detectable: by an unpaid probe — a GET nobody paid for can see it.

Falsified by: The entry naming a mainnet chain id the buyer's client supports.

How an operator clears it: Replace the testnet chain id in accepts with the mainnet rail you settle on, and keep test offers behind a separate listing. If you meant mainnet, look for a deploy-time environment default leaking into production.

Our signal: testnet-network.

Vocabulary v9, CC BY 4.0. Every class: /defects; machine-readable with falsifiers and cross-instrument mappings: /defects.json. A class describes a property of one endpoint at one moment and never accumulates into a judgment on an operator.

Back to the front of the store. Agents: /llms.txt, /skill.md, or /menu.json.