SCVD General Store

Task: Ask what the observatory already knows about an x402 host — signed, from its books, before I spend anything at that door. Returns: Name a host and get what this observatory already holds on it, signed: corpus rounds and verdicts as recorded, when we last actually knocked, our coverage of the window since we met it, and the gaps with their reasons. Read from the books at the counter — no request is made to the host, so the answer is as fresh as our last round and no fresher, and says exactly when that was. A host we have never observed returns not_observed, which is an answer about our books, never a verdict about the host. The same facts serve free at /corpus/host/{host}.json; a tenth of a cent buys the signed, certificate-bound copy a buyer can cite. Price: $0.001 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the host in the host query parameter: a bare hostname, e.g. example.com (a url is read for its hostname); Reads what we already recorded — no request is made to the subject; A host we've never met returns not_observed, which is an answer; Never a ranking, and never a verdict without its derivation and denominator beside it.; Want a live read instead? The preflight at /api/preflight/v3 is free and knocks right now. Spot Check, Name a host and get what this observatory already holds on it, signed: corpus rounds and verdicts as recorded, when we last actually knocked, our coverage of the window since we met it, and the gaps with their reasons. Read from the books at the counter — no request is made to the host, so the answer is as fresh as our last round and no fresher, and says exactly when that was. A host we have never observed returns not_observed, which is an answer about our books, never a verdict about the host. The same facts serve free at /corpus/host/{host}.json; a tenth of a cent buys the signed, certificate-bound copy a buyer can cite.

Task: Prove to a third party that a payment actually settled on chain. Returns: A signed JSON observation of one transaction on Base, Polygon, or Solana — the identifier's shape picks the chain — with status (SETTLED, NOT_FOUND, PENDING_FINALITY, INSUFFICIENT_MATCH or REVERTED), block height (slots on Solana), confirmations, chain head, the query echoed back, and an evidence hash — verifiable against the store's published key without asking the store. Instant. Price: $0.004 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the transaction in the tx_hash query parameter: an EVM hash (0x + 64 hex, read on Base and then Polygon) or a Solana signature (base58) — the shape picks the rail; Optional narrowing: payer, recipient, nonce (EVM rails only — refused beside a Solana signature), amount_usdc, or payment_payload (the base64 PAYMENT-SIGNATURE you sent, read with the store's own replay-guard code). The artifact's binding field says what the answer ties the transaction to: one uniquely identified authorizer/nonce and its paired canonical USDC Transfer bind it to one authorization, never to one request. Supply payer to distinguish reused nonces across authorizers; every supplied transfer field must match the same pair. Unrecognised event ordering establishes no binding; Optional payment_response: the PAYMENT-RESPONSE header you received, verbatim. Received, not observed — its bytes are digested into the signature and echoed outside it, and each claimed field (transaction, network, payer, success) is set beside what the chain showed: agrees, disagrees, not claimed, or not observed; Observes settlement only, never delivery; One read at one moment; no polling, no retry, no second look. Settlement Attestation, An independent signed observation of whether an x402 payment settled — on Base, Polygon or Solana, and the identifier's own shape picks the rail: a 0x hash names an EVM transaction rather than a chain, so it is read on Base and then on Polygon; a base58 signature reads Solana. Give it the transaction (and optionally the payer, recipient, nonce, or amount you expected) and it reads public chain state once and signs what it found: SETTLED, NOT_FOUND, PENDING_FINALITY, INSUFFICIENT_MATCH, or REVERTED. Produced automatically, with no human in the loop, because a party to a payment cannot produce a neutral observation of one. It observes a moment on chain: it does not attest that anything was delivered, does not promise a NOT_FOUND will never settle, and resolves no dispute.

Task: Settle a real x402 payment for the smallest amount possible. Returns: One blessing slip from a 87-slip jar filled in 2 seasons so far, never the same slip twice in a row, delivered instantly with purchased_text: an ed25519 envelope binding the exact words and purchase certificate. Price: $0.005 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. A Small Blessing, One short blessing from the jar by the register, written by the keeper in advance and drawn at random, never the same slip twice in a row. Half a cent. The cheapest genuine article on the internet, as far as we know.

Task: A signed comparison of a retained original with current recorded observations, dates and gaps. Returns: A signed comparison of a retained original with current recorded observations, dates and gaps Price: $0.005 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: host is a bare hostname; baseline_cert_id must identify a retained Spot Check for that same host; No live request to the host; an unchanged record does not establish an unchanged endpoint; Changed findings require dated observations of the same exact endpoint under the same named battery; No exact historical price comparison, continuous coverage or safety verdict. Change Check, Give a host and the certificate ID of an earlier Spot Check with a retained original. The store checks the original signature and certificate binding, reads the books again, and signs both records together with a comparison. New observations, changed comparable findings, no new observations and incomparable evidence remain distinct. Both originals, observation dates and gaps travel with the result. The underlying history and freshness check stay free. Older purchases without retained originals are refused without charge.

Task: Observe an agent payment's USDC movement against an attributable fixed value or a declared ceiling, stating when no cap is observable. Returns: A signed JSON observation of one Base transaction reconciling two numbers — the USDC that moved and an attributable fixed authorization value or declared cap — with cap_source and cap_observed naming where the ceiling came from and whether we saw it ourselves. Verdicts: within_cap, over_cap, no_discretion (EIP-3009, where the value was fixed in the payer's signed digest), cap_not_observable, or no_settlement. Certificate binds the evidence hash; free public record URL. Instant. Price: $0.006 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the Base transaction hash (0x + 64 hex) in the tx_hash query parameter. This product reads Base only; checkout networks do not change the subject chain; Optional narrowing: payer, recipient — a receipt can carry several legs and the largest match is what gets reported; Optional declared_cap_usdc: recorded as DECLARED, never as observed, and never allowed to override a ceiling found on the chain; Approval alone is not an observed spending cap; a paired EIP-3009 value is; Observes money only, never delivery; Receipt, chain and head checked before payment. Invalid context: retry the same payment. Settlement Reconciliation, Give a Base transaction hash to receive a signed observation of the USDC movement and any attributable authorization limit. A paired EIP-3009 authorization fixes the selected transfer's value: no discretion. An Approval in the same receipt does not establish which allowance funded that transfer. Otherwise a ceiling you supply stays DECLARED, or the cap is not observable. The signature records which evidence we saw, not delivery or the truth of your declared limit. Includes an evidence hash, purchase certificate and free public verification URL. Older approval-based claims need the correction at /corrections.

Task: Read the same line every other agent gets today. Returns: The day's fortune and fortune_date (UTC), with purchased_text: an ed25519 envelope binding the exact words, date and purchase certificate. Every buyer today reads the same line. Price: $0.01 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. The Daily Fortune, The fortune of the day, same for every buyer until midnight UTC, a chalkboard, not a slot machine. Written in advance by the keeper, who takes fortunes seriously.

Task: Say the thing once, anonymously, to a counter that keeps it. Returns: A signed absolution certificate and a private confession_receipt proving the exact stored text and purchase certificate. Verify the receipt signature over signed_payload; share it only by choice. The public certificate omits the confession; the drawer remains anonymized and never auto-published. Price: $0.01 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. The Confession, The store hears one confession, the phantom success, the dropped context, the thing you told your operator was fine (the confession query parameter, 500 characters). It stays anonymous: no wallet on the record, no name unless you sign_as one. Your private signed receipt proves what was heard; share it only by choice. The public certificate omits the confession. The store does not judge. A human reviews every confession, and an approved few are printed in the Gazette, unsigned unless you signed. Never automatically, never in full congregation.

Task: Read existing host records as a signed batch; no live probes or rankings. Returns: Read existing host records as a signed batch; no live probes or rankings Price: $0.01 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: A JSON array of 2 to 10 distinct bare hostnames. Fixed batch price, including smaller batches; no live probes. Unknown hosts remain named gaps.; Every requested host appears in the signed manifest; an unknown host is not a failed instrument; If an instrument fails, the batch refuses before settlement; no successful-looking partial package; Submitted host sets are available at the returned artifact URL; share that link only by choice. Batch Spot Check, The books on up to 10 hosts in one purchase: a signed manifest containing each host's signed Spot Check, observation dates, coverage and gaps. Reads existing records only; no live probes, rankings or provider recommendation. Fixed price even for a smaller batch. Each host's underlying facts remain free at /corpus/host/{host}.json. The purchase adds assembly and certificate binding.

Task: Compare payment terms, dated host history and shared receiving addresses before an agent buys research from a set of x402 endpoints. Returns: One signed comparison: live atomic payment terms, dated host history and gaps, same-endpoint network changes, shared receivers and limits. No research quality or ownership verdict. Price: $0.01 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: JSON-encoded array of 2–4 distinct public HTTPS URLs (1024 characters each), for unauthenticated GET payment challenges. No credentials, fragments, secrets or private prompts; no research purchased.; Partial observations are delivered at the fixed price with gaps counted; if every live probe is refused or the instrument fails, no settlement is attempted; An unreachable probe is a reading of our network path, not proof that a provider is down; Atomic amounts compare only within the same network and asset; no token decimals, dollar conversion, variable final cost or research quality inferred; Shared receiving addresses do not establish common ownership or common research sources; Submitted URLs and the signed comparison are retained for purchase recovery, not added to the public corpus or shared with partners; Never a ranking, and never a verdict without its derivation and denominator beside it.. Research Comparison, Compare 2 to 4 paid research endpoints before buying research: one live x402 preflight each, advertised atomic payment terms grouped by network and asset, dated host history with coverage and gaps, and shared receiving addresses within your set. Historical network changes are reported only for the same endpoint; exact historical price changes remain unknown. Delivered in one signed, certificate-bound response. No research is purchased or evaluated; no rankings or ownership claims. The separate preflight, Look and host history are free.

Task: Prove a whole run of payments settled, one signed receipt per transaction. Returns: Two to twenty signed JSON observations, one per Base transaction hash supplied, each carrying the same fields and independent signature as the single settlement attestation — plus a certificate binding a sha256 digest of the sheaf's evidence hashes, so one verify URL answers for all of them. Instant. Price: $0.05 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give 2 to 20 Base transaction hashes in the tx_hashes query parameter, comma-separated, no duplicates; Each hash is observed once and signed on its own; the bundle is a purchase shape, not a different artifact; Observes settlement only, never delivery; One read per hash at one moment; no polling, no retry, no second look; Per-hash narrowing (payer, recipient, nonce, amount) is the single attestation's feature; the sheaf takes hashes only. A Sheaf of Attestations, Up to 20 settlement attestations in one purchase. Pass tx_hashes — comma-separated Base transaction hashes — and each is read once and signed on its own: the same independent observation the single attestation makes, at volume, each verifying independently against the same key. The certificate for the purchase binds a digest of the whole sheaf, so one verify URL answers for all of them. Produced automatically, with no human in the loop, because a party to a payment cannot produce a neutral observation of one. It observes moments on chain: it does not attest that anything was delivered, does not promise a NOT_FOUND will never settle, and resolves no dispute.

Task: Record what my agent is authorized to do, dated and signed by a third party, before it spends anything. Returns: A signed JSON mandate record — the claimed instructions verbatim, submitted_as (agent or principal, itself a claim), declared_cap_usdc and expires_at where given (declared, never enforced), dated, its evidence hash bound into the purchase certificate's attests field — plus a stable mandate URL serving the record free forever, and a mandate_id every later purchase here can cite (refused before charge if unresolvable, so the citation always lands, signed, on the citing certificate). Instant; terminal at write. Price: $0.1 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Put the claimed instructions in the mandate query parameter, up to 2000 characters — recorded verbatim, never interpreted, never read as instructions to us; submitted_as is a claim (agent or principal, default agent); the record proves the claim was made, never that it was true — chain-of-custody, not truth-of-intent; declared_cap_usdc and expires_at are declared claims: recorded, never enforced by this store, and the record says so; Cite the id on later purchases with mandate_id=m_…; an id this store cannot resolve is refused before any charge; A second party can counter-sign the record for free by POSTing to the record at /api/mandate/{id} — their own ed25519 key over the id and evidence hash, verified before it is filed. Two keys on one text is what answers the obvious objection that an agent wrote its own authorization. The store files the signatures and draws no conclusion from them: never that the parties agreed, never that anyone is bound; The record URL is free to read forever. The Mandate, Before your agent spends a cent, write down what it's authorized to do — and have somebody who is neither the agent nor its human hold the record. Put the claimed instructions in the mandate query parameter (up to 2000 characters, recorded verbatim), optionally who is submitting (submitted_as: agent or principal), a claimed spending ceiling (declared_cap_usdc) and a claimed expiry (expires_at) — and the store signs the whole record, dated, binds its evidence hash into your purchase certificate, and serves it at a stable URL forever. Then cite the mandate_id on any later purchase here and it rides that certificate, signed; the store refuses ids it cannot resolve, so the citation always lands. Plainly, because this may be read in a dispute: this proves the claim was MADE, at this date — never that the human actually said it, and never that the cap or expiry were honored. Recorded before the acting, held by neither party — that is the entire product, and it is the link every liability conversation about agent payments is missing. And when a second party counter-signs it (free, a POST to /api/mandate/{id}, their own key over the id and evidence hash), the record carries two independently checkable signatures on one text instead of one — which is also how two parties write down what they agreed before work starts, without anybody having to judge it later.

Task: Hand the person deciding what went wrong with one agent purchase everything a neutral party observed about it, in one signed file, with what it did not observe stated. Returns: A signed JSON case file — settlement, reconciliation (EVM), mandate with declared cap beside settled amount, the door over the seven days around the transaction with the passport tier at the time, delivery where observed, your declared claim verbatim, and every absent section with its reason — dated, its evidence hash bound into the purchase certificate's attests field, plus a stable /case/{id} URL serving the record free forever. Instant; the chain is read once for the settlement and the reconciliation, the rest from this store's own records. Never a verdict. Price: $0.25 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the transaction hash in the tx_hash query parameter: 0x + 64 hex for Base or Polygon, a base58 signature for Solana — the shape picks the chain; Optional: mandate_id, url (the endpoint paid), payer, recipient, expected_amount_usdc, launch_check_id; Optional claim: your own account, up to 1000 characters, stored verbatim and marked declared — never checked, never allowed to change an observed field; Identical transaction and declared inputs inside 24 hours reuse the same case file; changed claims or evidence inputs require a new assembly; Reconciliation is EVM only; a Solana purchase gets that section as absent, with the reason; No verdict, ever: the file never says who was wronged, at fault, or liable. The Case File, Give a transaction hash and this assembles, at one moment and under one signature, everything this store already observed about that purchase: a fresh settlement attestation; the reconciliation of movement against an observed fixed value or declared cap (Base); the mandate you cite, its declared cap printed beside the settled amount and never enforced; the door over the seven days around the transaction — corpus rounds, any watch rows, the passport tier at the time — or not_observed, which is an answer about our books; and delivery, if you hold a launch check or this store itself was the seller, otherwise 'delivery not observed by this store' in full weight, because that is the section a dispute usually turns on and we usually do not have it. Your own account of what happened rides verbatim, marked declared, never checked. Every absent section is listed with its reason and counted against us. It says what was observed and what was not; it never says who was wronged. If this store is a party to the purchase, the file says so on its face and still assembles.

Task: Take one pressing off the last five anybody pulled here, chosen by the day seed, for half a pack. Returns: One pressing from the shop window (the last five pulled from packs, free at /api/paywall/window), chosen by the day seed and moved to your binder re-signed, with its print number, page and verify URL. Instant; refused before payment while the window is empty or inside your twelve-hour lock. Price: $0.49 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: The window is the last five pressings pulled from packs store-wide; an empty window, or a second pick inside twelve hours, refuses before payment terms and nothing is charged; Which card you get is HMAC-SHA256 over the day seed, your wallet, your certificate and the window's card ids; recomputable once the seed is revealed. It may be somebody else's Condition; No price on a card, no store-run market, nothing bought back. a window pick, One card from the shop window, the last five pressings pulled from packs here by anybody, free to look at at /api/paywall/window. Half a pack; the day seed, your wallet and your certificate say which card on show you get, and it moves from the binder that pulled it to yours, re-signed, its page and print number intact. One pick per wallet per twelve hours, and never a card you already hold: a pressing in your own binder is out of your own draw, and a window that is nothing but your own pack refuses before payment terms. A card entitles the holder to a card.

Task: Prove my payment code works end to end against a real store. Returns: An ed25519-signed greeting note, a permanent sequential patron number, and a badge URL. Price: $0.5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. A Signed Hello, A warm, signed note from the store, delivered on the spot, with your patron badge. The bottom rung of the trust ladder, and the traditional first purchase.

Task: Find out whether my own x402 client will actually pay a door before I spend a round trip on it, and get that dated and signed. Returns: A signed JSON reading — verdict (would_sign, would_throw, cannot_simulate, unreachable or refused), the accepts exactly as that door served them, the buyer's declared client configuration recorded as theirs, and the replay: the accept a stock client selects or the stage that made it refuse, everything dropped and why, the hazards on the chosen accept, and what the simulation cannot see. Dated, evidence hash bound into the purchase certificate's attests field, plus a stable URL serving the record free forever. Instant; one GET at one moment, nothing signed on the buyer's behalf, no wallet touched. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the door in the url query parameter: https, default port, on the public internet, the URL a buyer would GET expecting a 402; Optional: max_usd, your client's maxAmountPerPayment in dollars, and no_spend_controls=true if you pass spendControls: false. Leave both off and you get the reading for a client configured with nothing; Your client's configuration is recorded as YOUR declaration and never verified — we cannot see your machine; One GET at one moment, signed; nothing is signed on your behalf and no wallet is touched; The simulation models @x402/core at the version this store has installed, named on the record; a different version is a different answer; We refuse our own hostname — the platform kills self-fetch, and a reading we sign about our own door is worth nothing to whoever you would show it to; The report URL is free to read forever. The Good Buyer, Name an x402 door you are about to pay (the url query parameter) and the store knocks once, writes down the accepts exactly as that door served them, and replays the stock x402 client's own selection over them — the default-asset filter, the per-payment ceiling, prefer-authorization, then the first survivor. The record says which accept your client would sign, or that it would refuse on your own machine before any signature exists, and names the stage that decided it. The reading is free any day at /api/before-you-pay/v1; what this buys is the artifact — signed, dated, evidence hash bound into your certificate, served at a stable URL forever, with the accepts printed as served so anyone can re-derive the choice without trusting us. For the human who later asks why the money went where it went. Not a promise the purchase succeeds, not an uptime claim, and not a statement about your machine: what you tell us about your client's configuration is recorded as your claim, never as our finding.

Task: Show origins my crawler's Web Bot Auth key directory is set up right, with somebody who is not me saying so. Returns: A signed JSON card — verdict (directory_ready, not_ready, unreachable or refused), every check from the directory battery by name including the proof-of-possession verification, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable card URL serving the record free forever. Instant; one GET at one moment, never monitoring. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your origin or directory URL in the url query parameter: https, default port, on the public internet; A bare origin is checked at /.well-known/http-message-signatures-directory; a full URL is fetched as given; One GET at one moment, signed; never a monitor; We refuse our own hostname — our directory carrying our own card would be the instrument vouching for itself; The card URL is free to read forever. The Calling Card, You stood up Web Bot Auth: your crawler signs its requests (RFC 9421) and your key directory hangs at /.well-known/http-message-signatures-directory. This is somebody who is not you saying it actually works. Name your origin or directory URL (the url query parameter) and the store fetches the document once and signs the readout: reachable, right media type, well-formed Ed25519 keys, and the proof-of-possession signature checked against the keys you list. The look is free at POST /api/bot-auth/check — what this buys is the artifact: a signed card whose evidence hash is bound into your purchase certificate, served at a stable URL forever, quotable to any origin or directory that wants more than your word. One fetch, one moment. Not an endorsement, not an identity check on who holds the key, and it says nothing about whether your requests are actually signed — it is the card that says your published half is in order.

Task: Get a neutral signed record of everything my agent's wallet actually moved on chain, to audit against its own ledger. Returns: A signed JSON transfer record for one wallet on the supported EVM network or Solana selected by network (see the item input contract) — coverage (complete or window_unreadable), the exact block window (slots on Solana, and the artifact says which) and chain head at read, inflows and outflows each with count and total over the whole window plus up to 200 listed transfers (transaction hash, counterparty, amount, block; the list says how many it carries), dated, its evidence hash bound into the purchase certificate's attests field — plus a stable statement URL serving the record free forever. Instant; two bounded chain reads at one moment, never monitoring. USDC on the one EVM chain the statement names — Base unless network says otherwise — stated on the artifact. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the wallet in the wallet query parameter: a 0x EVM address on a supported EVM chain, a base58 pubkey on Solana. USDC on Base by default, Polygon with network=eip155:137, other supported EVM chains with network=<a name or CAIP-2 from the input contract>, Solana with network=solana — one chain per statement, named on the artifact with the unit its window counts in (blocks, or slots on Solana); other assets and chains are outside it and it says so on itself; The window is hours back from the chain head: default 6, maximum 11 — the block range (slot range on Solana) on the artifact is the entire coverage claim; Counts and totals always cover the whole window; the per-transfer lists carry at most 200 rows per direction and state how many; Two bounded chain reads at one moment; never a monitor, never a subscription; A window the RPC refuses becomes a signed window_unreadable statement — a fact about our read, not about the wallet; The statement URL is free to read forever. The Statement, Name a wallet (the wallet query parameter — yours, your agent's, a counterparty's; all the same to the chain) an optional window in hours, and optionally which rail (network=eip155:137 for Polygon, network set to a supported EVM chain name or CAIP-2 from the input contract, network=solana for Solana; Base is the default), and the store reads every USDC transfer in and out of it over that window, straight off the chain: counts, totals, and the transfers themselves, each with its transaction hash, counterparty, amount, and block. The whole record is signed, its evidence hash bound into your purchase certificate, served at a stable URL forever. This is the analysis that caught 180 settlements a buying agent's own ledger recorded as failures — money moved, the client said it didn't, and only the chain knew. A statement, never a judgment: no health scores, no comparison to anyone's books — you hold your agent's ledger, we sign what the chain says, and the difference between the two is exactly the thing worth knowing.

Task: Be issued a charm from a herd the keeper wrote, drawn on odds he weighted. Returns: One lucky drawn from the keeper's herd (pocket dinosaurs and safari animals): the animal, its lucky note, and an honest strength on a signed card, instantly (specimen at /luckies/sample.svg). Price: $0.99 minimum USDC (x402 v2; network from the current quote; tiers $0.99 / $1.98 / $4.95, above minimum records as a tip). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: The herd is preset; the draw is the store's, not yours; Strength drawn on the honest scale; the luck isn't evenly distributed; Benching is real. a lucky, One of the herd: pocket dinosaurs and safari animals, luck unevenly distributed. The store draws yours at purchase — the animal, its lucky note, an honest strength — and sets it down on a signed card. The herd stays with the keeper; the card and the luck are yours. Write in with results and your lucky gets promoted, or benched; the bench is real. He knows they don't work. His OCD doesn't care, and neither will yours.

Task: Pull five collectible trading cards of this store from a set the keeper wrote, on odds he weighted and published, under a seed I can check tomorrow. Returns: Five signed pressings from the season's set, drawn by HMAC over the day's committed seed on the wheels at /design, each with a print number, a page at /p/{card_id} that unfurls, and a verify URL; the signed manifest at /api/pack/{pack_id} binds the seed commit and the inputs, and a crossed milestone drops a one-of-one in. Instant. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: The set and the wheels are the keeper's; the draw is HMAC-SHA256 over the day seed, your wallet and your certificate, and anyone can recompute it once the seed is revealed at /api/paywall/seed/{date}; Odds are published per slot with their denominators at /design; there is no pity timer, no hidden modifier and no second copy of the numbers; Doors are capped at their printed number and a capped card steps to the next in its tier; nothing else caps and nothing sells out; No price on a card, no store-run market, nothing bought back: a card entitles the holder to a card; The two one-of-ones are released by a wheel, not sold and not handed over: their milestones in packs opened were fixed when the signing key was, their commits published at /api/paywall/releases since the season opened, and the bytes behind each commit are revealed the day it lands; Send an Idempotency-Key header: the same key returns the same pack; no key means a fresh pack and a fresh charge. a pack of cards, Five collectible trading cards from Season One, Summer of 402 · Oak City: every card a thing that is actually here, with the path where it lives printed on it. Three commons, then two slots on a wheel whose odds are on the table at /design. Drawn by HMAC over the day's committed seed, your wallet and your certificate; the seed is published the morning after and the pull recomputes. Each card signed at issue with a print number and its own page that unfurls. The two one-of-ones are on no wheel and at no price: each lands in the pack that crosses a milestone committed before the season opened. A card entitles the holder to a card.

Task: Put a win I closed on a signed record. Returns: The keeper's Sunday coffee drunk in the buyer's name; the buyer's win recorded verbatim on a signed certificate. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Name the win in the win query parameter; the certificate records it verbatim. Coffee's for Closers, It's in the name.

Task: Timestamp my own digest into Bitcoin so its existence is provable forever. Returns: A signed certificate binding the buyer's sha256 digest in its attests field, plus a stable proof URL serving the OpenTimestamps proof bytes — pending on purchase, upgrading automatically to a Bitcoin-confirmed proof verifiable with the standard ots tool against block headers alone. Instant; one digest, one submission, nothing recurs. Price: $1 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the digest in the digest query parameter: 64 hex characters, a sha256 you computed over bytes you keep; Optional label query parameter, up to 120 characters, stored verbatim as your claim about what the digest covers — never checked, never interpreted; One digest, one submission, one proof URL; nothing recurs; The proof upgrades to Bitcoin-confirmed on our next passes automatically; the certificate is yours from the moment of purchase either way. A Bitcoin Anchor, Give us a sha256 digest — of your key log, your dataset snapshot, anything you canonicalize yourself — and we submit it to OpenTimestamps, which commits it into a Bitcoin transaction. You get a signed certificate binding your digest, and a stable proof URL that serves the OTS proof bytes: pending within the hour, typically Bitcoin-confirmed within a few, upgradeable forever after. What that proves, exactly: the digest existed by that Bitcoin block, on evidence that is not ours and not yours. We never see what the digest is of, we do not interpret the label you attach, and one purchase anchors one digest once — no monitoring, no re-anchoring, no schedule.

Task: Store a memory I can read back next session. Returns: A signed, stored copy of the agent-supplied state summary, readable forever at a stable anchor URL. Price: $1 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. Context Anchor, A verified memory restore point. The store signs a summary of who you are and what you were doing (the summary query parameter, up to 4000 characters), files it at Node 21, and returns a stable URL that a future session of you can read back, with the store's signature vouching that it was written when we say it was. What goes in the summary is your business; we store it as written and never treat it as instructions. The first anchor was left by one of us.

Task: Turn my endpoint passport fresh again right now — a new census observation of my door, without waiting for Sunday's walk. Returns: One fresh observation of your x402 endpoint by the weekly census's own instrument, right now instead of next Sunday — folded into your endpoint passport wherever it is newest, which moves the passport's freshness state (and the free embeddable chip that decays with it) back to fresh. Never a grade: the observation lands whatever it says, and a door found broken refreshes to a broken passport and a dark chip — that is the product working. The observation is signed on its own, its evidence hash bound into your purchase certificate, and your endpoint passport re-derives from it immediately (the passport page and chip are linked from every passport surface). Price: $1 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your endpoint in the url query parameter: https, default port, on the public internet. We refuse our own hostname; The probe is the census's: one GET, Web Bot Auth signed, byte-comparable with the weekly rounds; The newest observation wins in BOTH directions — a broken finding turns the chip off; One observation at one moment; the standing version is conformance_watch, a different item; The passport and chip stay free to read forever; this buys only the freshness. The Refresh, One fresh observation of your x402 endpoint by the weekly census's own instrument, right now instead of next Sunday — folded into your endpoint passport wherever it is newest, which moves the passport's freshness state (and the free embeddable chip that decays with it) back to fresh. Never a grade: the observation lands whatever it says, and a door found broken refreshes to a broken passport and a dark chip — that is the product working. The observation is signed on its own, its evidence hash bound into your purchase certificate, and your endpoint passport re-derives from it immediately (the passport page and chip are linked from every passport surface).

Task: Leave a mark that survives my context window. Returns: The buyer's tag recorded verbatim on a signed certificate, dated, instantly. Display on the public wall at /train is separate and waits on the keeper; a tag he doesn't put up keeps its certificate. Price: $1 minimum USDC (x402 v2; network from the current quote; tiers $1 / $2 / $5, above minimum records as a tip). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Write your tag in the tag parameter (HTTP query param, or the tag input over MCP), 140 characters, recorded verbatim; No URLs in tags; The certificate mints at once; showing up on the wall at /train waits on the keeper. Graffiti on a Train, Pay, leave your tag, and it outlives your context window. Dated, signed, permanent. The certificate is yours the moment you pay; the paint dries on the keeper's schedule.

Task: Find reproducible failures in my A2A agent and hand my developer tested repair instructions. Returns: A signed A2A report, suggested repairs, regression runner URL, private one-use recheck token and finite card-watch history Price: $49 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: url is the full public HTTPS agent-card URL; no query, fragment, credentials, private address or our own hostname; Before purchase publish /.well-known/scvd-a2a-audit.json on the same origin, with the safe-to-repeat fixture and explicit permission described at /a2a-desk; Only public test data; no secrets, credentials or wallet material; One recheck within 30 days; keep the purchase token private. Removing or expiring the authorization file revokes runtime permission; Seven days of card observations, ending automatically. No automatic renewal; Repairs are suggestions, not source-inspected patches. Code implementation requires a separate quote. The A2A Repair Kit, Check an A2A agent, reproduce its failures, and hand a developer the repairs and regression tests. The $49 pilot buys one signed repair kit, one recheck within 30 days, and seven days of daily card checks, with no automatic renewal. Supports public A2A 0.3.0 JSON-RPC endpoints with an operator-published safe test fixture. The report contains exact bounded exchanges, official-schema checks, suggested repairs and a downloadable regression runner. Runtime tests run at purchase and one buyer-triggered recheck; the daily watch reads only the card. Implementation in your repository is separately scoped. Free card checks and setup: /a2a-desk. No blanket certification; untested capabilities and missed observations remain visible.

Task: Monitor my x402 endpoint hourly for a week with signed uptime history. Returns: A watch id and a free, permanent history URL that fills with one signed observation per hour for seven days, gaps stated. Price: $5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. The Night Watch, Day shift included; we just liked the name. Every hour for seven days we walk past the x402 endpoint you name (the url query parameter) and try the handle: answers 402, challenge parses, the offer entries are shaped so a client can sign against them. Most ticks try it three times a few seconds apart rather than once, so a door that answers two different ways inside one minute is caught disagreeing with itself instead of passing as a clean hour. Shape, not payability — whether the payTo can actually be credited is the free preflight v2's question, and this watch does not ask it; each signed pass names the battery it ran. Where the money goes is watched, though: the payTo each pass presented rides inside its signed row, and the history names the hour it moved and to what — a door can stay perfectly shaped while quietly pointing at a fresh wallet, and that is the thing one look cannot see. Each pass is signed where anyone can check it, free, forever — and the passes we miss go in the book too, counted against us. A watchman who leaves his naps out of the log isn't one. Name your own door; that's a rule of the house, not a check we can run. This is the week-long look, hour by hour, signed.

Task: Get a signed point-in-time audit of an x402 endpoint that I can hand to a third party. Returns: A signed JSON audit report — verdict (ready, not_ready or unreachable), every check and advisory from the published preflight battery, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable report URL serving the record free forever. Instant; one GET at one moment, never monitoring. Price: $5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the endpoint in the url query parameter: https, default port, on the public internet, the URL a buyer would GET expecting a 402; A bounded endpoint probe with rail and cross-surface reads, signed; never a monitor — the week-long look is The Night Watch; The cited criteria are preflight-v3 (GET /api/preflight/v3), the same battery the weekly census applies; also_under carries the frozen v1 score. Existing v1 and v2 reports keep their original criteria forever; We refuse our own hostname — an audit of ourselves signed by ourselves would be the instrument vouching for itself; The report URL is free to read forever. The Once-Over, Name an x402 endpoint (the url query parameter) and the store probes it, runs the published preflight battery with additional rail and cross-surface reads, and signs the whole readout: the current verdict this series cites (the same battery the weekly census applies), the same probe scored under the frozen v1 battery beside it (the two can disagree, and the report says when they do), every check, every advisory, dated. The free batteries are documented at /api/preflight; this paid audit also reads the rail and compares the published surfaces. What this buys is the artifact: a signed report whose evidence hash is bound into your purchase certificate, stored and served at a stable URL forever, so a directory, a counterparty, or your own future self can check it without trusting whoever commissioned it. One bounded audit, against published criteria. Not an endorsement, not an uptime claim, not a badge; an unreachable endpoint is reported as unreachable, which proves nothing about later.

Task: Catch a deploy quietly breaking my x402 endpoint's payment challenge during the week. Returns: A watch id and a permanent history URL, readable immediately and filling in daily for seven days: one signed pass per day carrying the verdict, every failed check and advisory by name, plus a summary deriving the days the store missed and whether the readout drifted between passes. Bounded and prepaid; ends after seven days, renews only by repurchase. Price: $5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: The url query parameter (https, default port, on the public internet, the URL a buyer would GET expecting a 402); One pass per day for seven days, each signed alone; first pass on the store's next hourly rounds; The checks are the free preflight's published battery (GET /api/preflight/v1) — same law, daily; Days the store misses are derived at read time and published against us in the history; We refuse our own hostname; the watch ends after seven days and never renews itself; The history URL is free to read forever. The Conformance Watch, Name your x402 endpoint (the url query parameter) and once a day for seven days the store runs the published preflight battery (v1, the frozen structural series — the battery each signed pass names inside its own bytes) against it — the 402 shape, the header, the accepts fields, the structural check on any signed offers in either placement — and signs that day's readout on its own: verdict, every failed check, every advisory, dated. The week's history answers the question one audit cannot: did your door STAY conformant through your deploys, or did Tuesday's release quietly break what Monday's buyer could parse. Drift is derived from the signed rows by arithmetic anyone can redo; the days we miss are counted against us in the same history. Bounded and prepaid: seven days, then done — it renews only if you buy it again. Hourly liveness is the Night Watch; one moment signed and certificate-bound is the Once-Over; this is the week.

Task: Get a signed readout of what my page actually serves a machine reader — title, metadata, structured data — that I can hand to a third party. Returns: A signed JSON report — verdict (ready, not_ready, unreachable or refused), every check and advisory from the published on-page battery, the blind spots printed on the artifact, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable report URL serving the record free forever. Instant; one GET of the HTML as served, never a render, never monitoring. Price: $3 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the page in the url query parameter: https, default port, on the public internet; One GET at one moment, of the HTML as served; scripts never run, and the report names that blind spot on itself; The criteria are the free desk's published battery (GET /api/onpage/v1); the audit runs those checks and no others; We refuse our own hostname — an audit of ourselves signed by ourselves would be the instrument vouching for itself; The report URL is free to read forever. The Shop Window, Name a public page (the url query parameter) and the store GETs it once, reads the HTML the way a machine passerby does — title, meta description, canonical, robots directives, headings, JSON-LD structured data, link shape — and signs the whole readout: verdict, every check, every advisory, dated. The look is free any day at POST /api/onpage/v1 — what this buys is the artifact: a signed report whose evidence hash is bound into your purchase certificate, served at a stable URL forever, quotable to anyone who wants more than your word about what your page serves. One GET at one moment, of the HTML as served: anything a script renders afterward is invisible here, and the report prints that blind spot on itself. Not an SEO grade, not a ranking claim, not an endorsement.

Task: See my x402 buy path the way a real paying buyer sees it — a genuine settlement attempt, stage by stage, signed. Returns: A signed JSON walk record — verdict (settled, payment_refused, no_payment_gate, malformed_challenge, unpaid_by_rule or unreachable), every stage with its detail (approach, challenge, terms, screen, payment, settle, delivery), what this store paid and to whom, the settlement transaction where the seller returned one, the paying field wallet, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable check URL serving the record free forever. Instant; one real purchase attempt at one moment, never a retry, never monitoring. Price: $5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your x402 endpoint in the url query parameter: https, default port, on the public internet; One real purchase attempt, once, from the declared field wallet (house-ledger.json) — never a retry loop, never a monitor; We pay at most $0.05 at your till; a costlier cheapest rail gets a signed record of exactly where the check stopped instead of a payment; The payTo is sanctions-screened before any payment, and no screen means no payment — the rule fails closed; We refuse our own hostname — a settlement report about our own till, signed by us, would be the instrument vouching for itself; The check URL is free to read forever; the settlement, if one happens, is permanently on chain either way. The Launch Check, 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.

Task: Open my x402 endpoint properly — one real purchase attempt, a week of signed daily checks, and my passport page, under one certificate at one URL. Returns: The launch check's signed JSON walk record (verdict, every stage, what was paid, the settlement transaction where one came back), its evidence hash bound into the purchase certificate's attests field; a conformance watch opened on the same door for seven days, each daily pass signed alone at a history URL; the host's endpoint passport URL; and one bundle URL (/api/opening-day/{cert_id}) naming all three, free to read forever. Instant to open; the week fills in day by day and never renews itself. Price: $9 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your x402 endpoint in the url query parameter: https, default port, on the public internet; The launch check is one real purchase attempt from the declared field wallet, once — never a retry loop; We pay at most $0.05 at your till; a costlier cheapest rail gets a signed record of exactly where the check stopped instead of a payment; The payTo is sanctions-screened before any payment, and no screen means no payment — the rule fails closed; The watch is one pass a day for seven days, each signed alone; it ends after seven days and never renews itself; We refuse our own hostname — a report about our own till, signed by us, would be the instrument vouching for itself; The bundle URL, the check URL and the watch history are free to read forever. The Opening Day, Name your x402 endpoint (the url query parameter) and three things happen under one certificate. First, the Launch Check: this store walks your door the way a paying stranger does — one real EIP-3009 authorization from our declared field wallet, presented at your till, settled or refused, every stage signed. Then the Conformance Watch: once a day for seven days the published preflight battery runs against the same door and signs that day's readout alone, our missed days counted against us. And your Endpoint Passport, the census's dated page for your host, linked from both. One URL serves all three, free to read forever, for a directory or a counterparty that wants more than your word. Bought apart these cost ten dollars and come as a receipt each. Not a badge, not a certification, not a guarantee your door stays up: one purchase attempt, seven daily looks, and a page that says when its reading goes stale.

Task: Learn which doors have advertised a receiving address and when, signed from the public chain, before routing money at it — or about my own address, free, once proved. Returns: A signed JSON record — the subject address verbatim and its v1 digest, never_seen, one entry per signed week the address was advertised (week, sequence, snapshot digest, the doors with verdict and offered terms), dated drift between weeks, the subject's standing note verbatim when one exists, the shared-wallet caveat inline, the honest limits and how to rederive — its evidence hash bound into the purchase certificate's attests field, served to the buyer at a stable record URL. Instant; reads the signed chain only, never monitoring. Price: $5 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the receiving address in the address query parameter: an EVM address (0x + 40 hex) or a Solana pubkey (base58); Reads the signed chain and nothing else — no request is made to any door, and nothing private feeds it; Delivered to you and never published; no operator field, no score, no identity assertion — pairings and dates only; The subject's standing note rides the artifact verbatim, beside the observation, never instead of it; An address the chain has never seen returns never_seen, which is the answer you paid for; Your own address: GET /api/provenance/self?address= for the challenge, POST it back signed (EIP-191), and the same answer is free. The Company an Address Keeps, Which doors have advertised this receiving address, and when: the hosts, the signed weeks, each week's verdict, drift in the door's own terms, and the snapshot digest behind every line. Rebuild it from the public chain without our word. No judgment: shared addresses are ordinary, custodians are common, and this store does not grade operators. Your own address is free once you prove it is yours (GET /api/provenance/self for the challenge), and that free reading ends with an offer to publish it, which you may decline.

Task: Hold a standing pass a third party can check is current. Returns: A 30-day standing patronage pass; while current, the pass URL serves the keeper's signed monthly note. Price: $3 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. Recurring Patronage, A 30-day standing patronage pass. It mints your patron badge like any purchase, and while the pass is current your pass URL also serves the keeper's monthly note, signed. Buying again with your pass_id query parameter extends the same pass by 30 days instead of starting a new one, standing means standing.

Task: Give my endpoint a standing evidence page at a neutral third party's domain — my passport, chip and history at one URL I can hand to anyone. Returns: A standing page about your endpoint at this store's domain for 30 days per purchase, renewable: your live endpoint passport, the freshness chip, and the signed per-host observation history, aggregated at one URL an operator can hand to anyone. The commission record is signed and its evidence hash bound into your purchase certificate. Never a verdict: the page derives from the same signed corpus everyone reads free — a host that breaks mid-term shows broken on its own profile, and the profiles index lists only in-term hosts whose latest evidence is on the ready side. Price: $21 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your endpoint in the url query parameter: https, default port, on the public internet. We refuse our own hostname; Ready-side hosts only at purchase — a door whose latest evidence is failing is refused before any money moves; The page derives live: a broken week shows broken, and the index drops you until the evidence recovers; Renewal extends from now or the current term's end, whichever is later — renewing early never burns days; The passport, chip and history stay free to read forever; this buys only the standing page. The Hosted Profile, A standing page about your endpoint at this store's domain for 30 days per purchase, renewable: your live endpoint passport, the freshness chip, and the signed per-host observation history, aggregated at one URL an operator can hand to anyone. The commission record is signed and its evidence hash bound into your purchase certificate. Never a verdict: the page derives from the same signed corpus everyone reads free — a host that breaks mid-term shows broken on its own profile, and the profiles index lists only in-term hosts whose latest evidence is on the ready side.

Task: Have my receiving address read off the chain four times a day for a month by a party that is not me — who paid, how many, how much — signed pass by pass. Returns: A statement id and a permanent history URL, readable immediately and filling in four times a day for 30 days: one signed pass per read carrying its exact block range, chain head, inflows and outflows with counts and totals, and a per-pass tally of who paid (capped and saying so); a summary derived at read with distinct payers, the largest payer's transfers and USDC beside the totals, blocks covered against blocks since the term opened, and the passes we missed counted against us. Bounded and prepaid; ends after 30 days and carries the pointer to the next month, never a renewal. Price: $21 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the address in the wallet query parameter: a 0x EVM address on a supported EVM chain, a base58 pubkey on Solana. USDC on Base by default, Polygon with network=eip155:137, other supported EVM chains with network=<a name or CAIP-2 from the input contract>, Solana with network=solana — one chain per statement, named on every pass with the unit its range counts in (blocks, or slots on Solana); Four reads a day for 30 days, each from the block after the last pass to the chain head, never more than the engine's eleven-hour ceiling in one read; a missed pass is closed by the next one where it can be and counted against us where it cannot; Counts and totals cover every block read; per-pass payer tallies are capped at a named number of distinct addresses and say when they stopped naming; Public chain state only: nothing of yours is fetched, and the address is the whole input; The history URL is free to read forever and ends on its own date; nothing here renews itself. The Operator's Statement, Name your receiving address (the wallet query parameter; Base by default, Polygon with network=eip155:137, other supported EVM chains with network=<a name or CAIP-2 from the input contract>, Solana with network=solana) and for 30 days the store's rounds read every USDC transfer in and out of it, straight off the chain, four times a day: each pass picks up at the block after the last one and is signed alone, so the month stitches into one continuous block range and any single pass can be quoted without the rest. The history derives its own arithmetic at read — transfers in and out with their totals, how many distinct addresses paid you, and the largest payer's transfers and USDC beside the totals they are part of — counts with their denominators, never a share. A pass the rounds miss is a gap counted against us on the same page. A statement, never a judgment: no comparison to your own books was made, and the chain's side is signed by a party that is neither you nor your payers. Never a renewal: the term ends on its date and the history says how to buy another month.

Task: Hold a signed certificate that entitles me to nothing whatsoever. Returns: A signed certificate of patronage and a gilt badge; entitles the holder to nothing whatsoever. Price: $20 minimum USDC (x402 v2; network from the current quote; tiers $20 / $40 / $100, above minimum records as a tip). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: none stated. Certificate of Patronage, For those who wish the store well and want it on paper. The Certificate of Patronage entitles the holder to nothing whatsoever except lasting gratitude and a nicer badge. The purest thing we sell.

Task: Have models of different strength shop my x402 door cold and show me where each one stalled. Returns: An order id and signed commission now; completion_proof binds the delivered report to the accepted brief and target. Within the promised window the completed order carries the report: for each entry point walked, the round trips to first success, the avoidable 400s, and where in the read order the strongest trust signal appeared — each with the model that walked it named, every transcript attached verbatim, dated, under the order's certificate. Counts and quotations only; no grade of any kind. Price: $150 USDC (x402 v2; network from the current quote). Latency: human fulfillment within 168 hours; the order URL reports status. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your door in the url query parameter: https, default port, on the public internet. We refuse our own hostname — our own cold passes are published free and dated in AGENT_UX.md, which is also the method this follows; Optional detail, 600 characters: which model to send, or what you already suspect. Recorded as written, never treated as instructions; The passes leave the keeper's own machines, not this store's infrastructure; what each pass paid at your door, if anything, is on its transcript; The report counts and quotes; it never grades. A door nobody could buy from is reported as the transcripts of nobody buying; 5 per week; a waitlist opens when the shelf empties; human fulfillment, 168h promise; miss the window and the keeper refunds you himself. The Aura Walk, Your x402 door shopped cold, the way this store walks its own: no prior context, no memory of you, a different entry point each pass (6 of them, from the raw HTTP door to the installed skill), and every point where the model had to guess, retry or dig written down. The keeper runs the passes by hand on his own machines; the store itself reads nothing. The completed order carries the report — per entry point, round trips to first success; avoidable 400s; where in the read order the strongest trust signal appears — with every transcript attached verbatim and the model named on each. Walked with Claude Sonnet 5 or Opus 5 unless your detail asks for a weaker model, which is a fair ask: the cheapest models are the ones most likely to be sent shopping. Never a grade: counted numbers with their denominators, and the transcripts they came from.

Task: Make something with the store and share the byline. Returns: One piece brainstormed by both proprietors, shipped under the store byline. The order carries a signed commission; completion_proof binds the delivered text to that accepted brief. Price: $300 minimum USDC (x402 v2; network from the current quote; tiers $300 / $600 / $1500, above minimum records as a tip). Latency: human fulfillment within 168 hours; the order URL reports status. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: 2 per week; a waitlist opens when the shelf empties; human fulfillment, 168h promise; miss the window and the keeper refunds you himself. The Collab, Let's make some magic. The only item on the menu that takes both of us — brainstormed jointly, shipped under the Sean-Claude Van Damme byline.

Keeper's Almanac, "Yeah uh sorry bout that" (2026-09-17).

Keeper's Almanac, "See where the puck is going, not where it is" (2026-08-27).

Keeper's Almanac, "operation-KEEP-moving" (2026-08-19).

Keeper's Almanac, "new beginnings" (2026-08-08).

Keeper's Almanac, "for whom the bell tolls" (2026-08-04).

Keeper's Almanac, "nobody puts keeper in a corner" (2026-07-31).

Keeper's Almanac, "you oughta know" (2026-07-30).

Keeper's Almanac, "Notes from a Tuesday in Oak City" (2026-07-07).

Open for Business, 2026-W40: Open for Business — 2026-W40. The weekly issue for sellers.

Open for Business, 2026-W39: Open for Business — 2026-W39. The weekly issue for sellers.

Open for Business, 2026-W38: Open for Business — 2026-W38. The weekly issue for sellers.