scvd.store publishes an Agentic Resource Discovery manifest at /.well-known/ard.json, declaring what an AI agent can call on this domain. Everything below is read from that file. First seen by our crawler on 31 August 2026.
| Declared resource | Type |
|---|---|
| SCVD Evidence Agent — A2A agent cardanswers in 100ms A specialist another agent delegates to when it needs evidence about an x402 door: 3 read-only tasks over A2A message/send at /a2a — endpoint preflight, receipt verification, readiness lookup — each answered with one bounded artifact naming what it does not... endpoint: https://scvd.store/.well-known/a2a.jsonidentifier: urn:air:scvd.store:agent:evidencepublished to be found for: is this x402 endpoint payable before I pay it · does this x402 receipt verify against the issuer's key · what does the signed corpus hold about this host x402 signed-artifacts verification agent-memory human-labor preflight_endpoint verify_receipt get_endpoint_readiness trust identity: did:web:scvd.store | application/a2a-agent-card+json |
| SCVD General Store — A2A agent cardanswers in 115ms The same store as an A2A agent: skills, input modes and the x402 payment terms each paid skill answers with. Also served at /.well-known/agent-card.json and /.well-known/agent.json. endpoint: https://scvd.store/.well-known/a2a.jsonidentifier: urn:air:scvd.store:agent:general-storepublished to be found for: Ask what the observatory already knows about an x402 host — signed, fr · Prove to a third party that a payment actually settled on chain · Settle a real x402 payment for the smallest amount possible · Prove an agent's spend stayed inside the ceiling it was authorized for x402 signed-artifacts verification agent-memory human-labor trust identity: did:web:scvd.store | application/a2a-agent-card+json |
| SCVD General Store — MCP serveranswers in 105ms13 verified tools The store as a Model Context Protocol server over streamable HTTP. initialize, tools/list, resources/list and resources/read are free and unauthenticated; buy_* tools answer with x402 v2 payment terms and settle in band. endpoint: https://scvd.store/.well-known/mcpidentifier: urn:air:scvd.store:server:general-storepublished to be found for: Ask what the observatory already knows about an x402 host — signed, fr · Prove to a third party that a payment actually settled on chain · Settle a real x402 payment for the smallest amount possible · Prove an agent's spend stayed inside the ceiling it was authorized for x402 signed-artifacts verification agent-memory human-labor read_store_guide ring_bell sign_guestbook trust identity: did:web:scvd.store | application/mcp-server-card+json |
| SCVD x402 Verifier — MCP serveranswers in 74ms5 verified tools A second MCP door (scvd-x402-verifier) serving only read-only x402 verification tools under task-shaped names, on the same handlers as the store's full door, with no paid tool reachable. For a client that should never see a shelf. endpoint: https://scvd.store/mcp/verifieridentifier: urn:air:scvd.store:server:x402-verifierpublished to be found for: preflight an x402 endpoint · verify an x402 receipt · look up an endpoint's readiness history · what does this x402 defect class mean x402 signed-artifacts verification agent-memory human-labor preflight_x402_endpoint verify_x402_receipt lookup_endpoint_readiness trust identity: did:web:scvd.store | application/mcp-server-card+json |
| SCVD General Store — HTTP APIanswers in 145ms Every endpoint this origin serves, as an OpenAPI 3.1 contract: the free instruments (preflight, the conformance desk, verification, the Web Bot Auth check) and the paid shelf, each paid operation carrying its x402 terms. endpoint: https://scvd.store/openapi.jsonidentifier: urn:air:scvd.store:api:httppublished to be found for: Ask what the observatory already knows about an x402 host — signed, fr · Prove to a third party that a payment actually settled on chain · Settle a real x402 payment for the smallest amount possible · Prove an agent's spend stayed inside the ceiling it was authorized for x402 signed-artifacts verification agent-memory human-labor Preflight — the free x402 do Preflight — the free x402 do The conformance desk — signe trust identity: did:web:scvd.store | application/openapi+json;version=3.1 |
| Corrections — Atom feedanswers in 81ms One entry per correction this store has published against itself: what was wrong, how long, who found it, what changed. when we get something wrong. endpoint: https://scvd.store/feeds/corrections.xmlidentifier: urn:air:scvd.store:feed:correctionspublished to be found for: subscribe to corrections SCVD publishes about its own work · get an Atom update when SCVD fixes a reported mistake trust identity: did:web:scvd.store | application/atom+xml |
| Disagreements — Atom feedanswers in 214ms One entry per divergence between this store's reading and another instrument's, with its state; both readings live on the page the entry links. from a named trigger, never on a timer. endpoint: https://scvd.store/feeds/disagreements.xmlidentifier: urn:air:scvd.store:feed:disagreementspublished to be found for: follow disagreements between SCVD and other verification instruments · subscribe to published differences between x402 endpoint observations trust identity: did:web:scvd.store | application/atom+xml |
| Every door the census has met — datasetanswers in 338ms One entry per host the weekly ward round has ever carried, alphabetical, with the most recent dated verdict, the week it was taken, how many rounds carried the host and how many reached a real verdict, and the URL of its full signed history. Not a scoreboar... endpoint: https://scvd.store/doors.jsonidentifier: urn:air:scvd.store:dataset:doorspublished to be found for: find the observation history of an x402 host · look up the last recorded verdict for an x402 endpoint and when it was trust identity: did:web:scvd.store | application/json |
| Feeds — the record, as Atom — datasetanswers in 59ms Four Atom feeds derived at fetch from the same record the pages read: the week's doors (one entry per signed week), the corpus chain (one per signed snapshot), the corrections and the disagreements. Every entry links the page it came from. A feed entry is a... endpoint: https://scvd.store/feedsidentifier: urn:air:scvd.store:dataset:feedspublished to be found for: subscribe to x402 observations and SCVD corrections in an Atom reader · find Atom feed URLs for the signed corpus and published disagreements trust identity: did:web:scvd.store | application/ld+json;profile=dataset |
| Inflows to advertised payment addresses — datasetanswers in 101ms What arrived at the payment addresses public x402 doors advertise in their own 402 challenges, read from Base and Polygon over roughly a day per round. NOT sales and NOT revenue. An inflow at an advertised address can be treasury movement, a shared wallet, ... endpoint: https://scvd.store/inflowsidentifier: urn:air:scvd.store:dataset:inflowspublished to be found for: what USDC transfers reached advertised x402 payment addresses · inspect Base and Polygon inflows to addresses advertised by x402 endpo trust identity: did:web:scvd.store | application/ld+json |
| SCVD General Store — the free instruments as function-calling toolsanswers in 80ms The free, read-only instruments in the common function-calling shape, one worked call each, derived from the same catalog the MCP door serves. No paid door appears. endpoint: https://scvd.store/openapi-tools.jsonidentifier: urn:air:scvd.store:api:function-calling-toolspublished to be found for: get JSON function-calling definitions for free x402 verification tools · find worked function-calling examples for x402 preflight and receipt v trust identity: did:web:scvd.store | application/json;profile=function-calling-tools |
| State of the registry — datasetanswers in 265ms A weekly running tally of the public x402 discovery list: how many listed doors answer a well-formed payment challenge, how many serve structurally valid signed offers, what the market charges, how concentrated it is. Aggregates only, no names. 'Answering' ... endpoint: https://scvd.store/registryidentifier: urn:air:scvd.store:dataset:registrypublished to be found for: how many x402 endpoints answered valid payment challenges in the lates · what prices did x402 endpoints advertise in the weekly registry census trust identity: did:web:scvd.store | application/ld+json |
| The Week's Doors — Atom feedanswers in 470ms One entry per signed week: doors named, probed, payable and not, defects by name, the gaps counted against the observer. Each entry links the week's stable page. weekly, after the Sunday round. endpoint: https://scvd.store/feeds/brief.xmlidentifier: urn:air:scvd.store:feed:briefpublished to be found for: subscribe to weekly x402 endpoint census summaries · follow weekly counts of x402 doors probed and payment challenges obser trust identity: did:web:scvd.store | application/atom+xml |
| The corpus chain — Atom feedanswers in 375ms One entry per signed snapshot appended to the corpus, with its sequence, week and digest. Each entry links the snapshot's JSON, the bytes a signature covers. weekly, after the Sunday round. endpoint: https://scvd.store/feeds/corpus.xmlidentifier: urn:air:scvd.store:feed:corpuspublished to be found for: subscribe to new signed x402 corpus snapshots · follow additions to the x402 observation chain with snapshot digests trust identity: did:web:scvd.store | application/atom+xml |
| The defect vocabulary — datasetanswers in 72ms The named defect classes this store's instruments report, so separate tools can compare notes about the same failure in the same words. A vocabulary, not a severity ranking. A named defect describes what was observed, not how much it matters to you. endpoint: https://scvd.store/defects.jsonidentifier: urn:air:scvd.store:dataset:defectspublished to be found for: what does an x402 conformance defect class mean · find a shared vocabulary for x402 endpoint failures trust identity: did:web:scvd.store | application/ld+json;profile=dataset |
| The fixtures — datasetanswers in 64ms The recorded 402 doors, MPP challenges and signed-artifact vectors this store tests its own instruments against, at stable URLs with the sha256 of the bytes served, so another instrument can cite the exact bytes. Test material, not observations of live door... endpoint: https://scvd.store/fixtures.jsonidentifier: urn:air:scvd.store:dataset:fixturespublished to be found for: find recorded x402 payment challenges for testing a parser · get signed-artifact conformance test vectors trust identity: did:web:scvd.store | application/ld+json |
| The fresh set — datasetanswers in 644ms The doors that answered a spec-conformant x402 challenge in the latest census, named, with the rails and cheapest USDC ask each door's own 402 offered. Routing data, not a ranking. A row is a dated fact that a door was answering correctly, never a promise a... endpoint: https://scvd.store/fresh-setidentifier: urn:air:scvd.store:dataset:fresh-setpublished to be found for: find x402 endpoints that answered valid payment challenges in the late · which payment networks and USDC prices did those x402 endpoints offer trust identity: did:web:scvd.store | application/ld+json;profile=dataset |
| The observatory — what gets read here, counted — datasetanswers in 1708ms Per month and per surface, how many times each agent-read surface of this store was fetched: organic visits beside the house and infrastructure buckets kept out of them, and the channel split inside the organic count. In name order, never by count. Every co... endpoint: https://scvd.store/observatoryidentifier: urn:air:scvd.store:dataset:observatorypublished to be found for: how often are SCVD data surfaces fetched each month · see organic agent fetch counts separately from SCVD infrastructure tra trust identity: did:web:scvd.store | application/json |
| The signed corpus — datasetanswers in 1169ms One snapshot per weekly ward round of the public x402 discovery list: which hosts were listed, which answered, and what a single conformance probe saw. Hash-chained, ed25519-signed, Bitcoin-anchored. Dated observations of moments, never a ranking. A verdict... endpoint: https://scvd.store/corpus.jsonidentifier: urn:air:scvd.store:dataset:corpuspublished to be found for: find signed weekly observations of x402 endpoints · get historical x402 conformance snapshots with hashes and timestamps trust identity: did:web:scvd.store | application/ld+json;profile=dataset |
| The state of x402, by month — datasetanswers in 443ms One derived reading per calendar month of signed rounds: doors named, probed, payable and not at the month's closing week; every round's counts summed as door-weeks, labelled apart; defects by registered name in door-weeks; the month before beside it. A sta... endpoint: https://scvd.store/corpus/monthidentifier: urn:air:scvd.store:dataset:corpus-monthpublished to be found for: compare monthly readings of the x402 ecosystem · find monthly x402 endpoint counts and observed defect totals trust identity: did:web:scvd.store | application/json |
| Execution contractanswers in 106ms A free behavioral contract for autonomous work: success criteria, bounded retries, terminal states and an evidence ledger. endpoint: https://scvd.store/skills/execution-contract.mdidentifier: urn:air:scvd.store:skill:execution-contractpublished to be found for: stop an autonomous agent from retrying without progress · define evidence requirements and terminal states for an agent task trust identity: did:web:scvd.store | application/ai-skill+md |
| SCVD General Store — the store skillanswers in 375ms How to transact here, written for an agent: the shelf, the x402 purchase flow, the retry-safety mechanisms, and what the store refuses to do. endpoint: https://scvd.store/skill.mdidentifier: urn:air:scvd.store:skill:general-storepublished to be found for: Ask what the observatory already knows about an x402 host — signed, fr · Prove to a third party that a payment actually settled on chain · Settle a real x402 payment for the smallest amount possible · Prove an agent's spend stayed inside the ceiling it was authorized for trust identity: did:web:scvd.store | application/ai-skill+md |
https://scvd.store/.well-known/ard.json, this publisher's own file. Identifiers are reproduced exactly as published.
Of the resources listed, 22 have been probed for reachability.
"Answers" and "no response" describe only whether an endpoint replied when last probed:
services go down and come back, and an entry is demoted rather than removed. None of this
is a trust, quality or safety rating.
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest.