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

Offer a buyer cannot sign against — x402 defect class unsignable-offer

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: Every accepts entry carries the fields a client needs to construct a payment, as strings.

What a buyer loses when it is present: A buyer reaches the signing step and has nothing to sign. Indistinguishable, from the seller's logs, from nobody wanting the goods.

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

Falsified by: Every accepts entry carrying the published required fields at the stated moment.

How an operator clears it: Fill every accepts entry with the v2-required fields, as strings, and regenerate the offer from your server's own config rather than hand-editing JSON. The free preflight names the missing field.

Our signal: accepts.

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.