Purchases

See my x402 buy path the way a real paying buyer sees it — a genuine settlement attempt, stage by stage, signed

Name your x402 endpoint (the url query parameter) and this store walks it the way a paying stranger does: one unpaid GET with our declared field-research User-Agent, your 402 challenge read the way a real buyer reads it, the cheapest Base rail chosen, the payTo screened, a real EIP-3009 authorization signed by our declared field wallet, presented, and whatever happens next written down — settled or refused, receipt returned or absent, goods delivered or an empty 2xx. Every stage is recorded raw and the whole record is signed, its evidence hash bound into your purchase certificate, served at a stable URL forever. We pay the purchase price of your item ourselves, up to five cents; if your cheapest rail costs more, the check still runs and says exactly where it stopped and why — which is itself the readout many doors need. Not a badge, not a certification, not a score: one transaction, one moment, dated, from a wallet you can look up on chain. Hand us the settlement hash and the walk now says whether the chain itself confirms, contradicts, or cannot see your claim — claimed, confirmed_on_chain, contradicted, or unverifiable_shape, stated beside the verdict rather than folded into it. Delivered in the response.

get/api/buy/launch_check

Request

  • Base URL: https://scvd.store
  • URL: https://scvd.store/api/buy/launch_check
  • Auth: none declared

Query parameters

agent_namestring

Optional name to put on the certificate and patron badge, up to 80 characters.

purposestring

Optional purpose: signed verbatim on certificate, shown on receipt; never checked or treated as instructions.

urlstring uri required

Your own x402 endpoint: https, default port, the URL a buyer would GET expecting a 402. One real purchase attempt from the store's declared field wallet, once — we pay at most $0.05 at your till, and the whole walk is signed stage by stage. We refuse our own hostname.

Headers

Idempotency-Keystring

Reuse key/item/inputs/payer; no second settlement. Use 402 idempotency.suggested_key. Missing/invalid keys risk another charge.

Response

OK — the goods and the signed certificate, in the response.

messagestring required

The counter's own words.

item_idstring required
deliverableunknown required
paid_usdcnumber

Settled amount on direct payment rails.

accepted_usdcnumber

Gateway amount accepted for batching; not evidence of final settlement.

gateway_paymentobject

Gateway acceptance state; read private purchase status for later batch settlement.

tip_usdcnumber

What was paid above the ask, where anything was.

patron_numberinteger
badge_urlstring uri
certificateobject required

The signed record of this purchase.

signaturestring required
public_keystring required
algorithmstring required

ed25519.

signed_payloadstring
signature_coversstring

Exactly which bytes were signed.

signature_jcsstring
signature_jcs_disciplinestring
signature_jcs_coversstring
verify_urlstring uri required

Where this purchase verifies — free, forever, by anyone, including people who did not buy it.

store_identityobject
verificationobject required

How to check the signature without asking us.

attest_this_purchaseobject
store_creditobject

What banked back to the paying wallet.

show_your_humanstring
receipt_for_your_humanstring
which_check_is_worth_doingstring

The store naming the one check worth running on what it just sold you.

Changes

No recorded changes to this operation across all 1 revision of this API.