SCVD General Store .well Known API

The .well Known API from SCVD General Store — 11 operation(s) for .well known.

Operations 11

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /.well-known/oauth-protected-resource Read the protected-resource metadata · Protected-resource metadata (RFC 9728) #
Ask an LLM
“Does this store publish RFC 9728 protected-resource metadata?”
“Is there an OAuth authorization server gating the store's resources?”
Tell an agent
Fetch the store's OAuth protected-resource metadata.
Show me what gates this resource according to RFC 9728.
GET /.well-known/api-catalog Read the RFC 9727 API catalog · The API catalog (RFC 9727) #
Ask an LLM
“Which API surfaces does this origin serve, as an RFC 9727 linkset?”
“Where is each API's OpenAPI contract and status link listed?”
Tell an agent
Get the store's API catalog.
List every API surface and its service-desc link from the api-catalog.
GET /.well-known/ard.json Read the Agentic Resource Discovery manifest · Agentic Resource Discovery manifest #
Ask an LLM
“What agentic resources does the store publish in its ARD manifest?”
“Where can a registry find the MCP server, A2A card and skills in one file?”
Tell an agent
Fetch ard.json.
Show me the agentic resource discovery entries this origin publishes.
GET /.well-known/ai-catalog.json Read the ARD manifest at its predecessor path · ARD manifest (predecessor path) #
Ask an LLM
“Is ai-catalog.json still served for scanners that know only the old path?”
“Does the legacy ai-catalog.json match ard.json byte for byte?”
Tell an agent
Fetch the legacy ai-catalog.json manifest.
Read the predecessor-path copy of the ARD manifest.
GET /.well-known/mcp.json Read the MCP manifest at the .json alias · The MCP server manifest (.json alias) #
Ask an LLM
“Is the MCP manifest also available at mcp.json?”
“Which scanners need the .json alias of the MCP manifest?”
Tell an agent
Fetch /.well-known/mcp.json.
Read the MCP server manifest from its .json alias.
GET /.well-known/http-message-signatures-directory Read the store's Web Bot Auth key directory · This store's own Web Bot Auth key directory #
Ask an LLM
“Which ed25519 key does the store sign its outbound probes with?”
“Can I verify requests from the store's crawler with its published JWK Set?”
Tell an agent
Fetch the store's http-message-signatures directory.
Get the key set the store uses to sign its probes.
GET /.well-known/x402 Read the minimal x402 discovery listing · x402 discovery (minimal) #
Ask an LLM
“What is the de-facto x402 indexer entry point for this store?”
“Which priced resources does the minimal x402 discovery file list?”
Tell an agent
Fetch /.well-known/x402.
Read the store's minimal x402 discovery document.
GET /.well-known/x402.json Read the full x402 catalog of payable resources · x402 discovery (full) #
Ask an LLM
“Where is the richer origin-hosted catalog of payable x402 resources?”
“Does x402.json carry more detail than the minimal discovery file?”
Tell an agent
Fetch /.well-known/x402.json.
Get the full x402 catalog with every payable resource.
GET /.well-known/mcp Find where the MCP server is · Where the MCP server is #
Ask an LLM
“Where is the store's MCP endpoint and which protocol versions does it negotiate?”
“Which MCP methods answer without payment?”
Tell an agent
Fetch /.well-known/mcp.
Tell me the MCP endpoint, its capabilities and the initialize request to send.
GET /.well-known/agent-instructions Read when an agent should use this store · When to reach for this store #
Ask an LLM
“When should my agent reach for this store, and when does it not need it?”
“Which items answer which situations, with the exact request to make?”
Tell an agent
Fetch the store's agent instructions.
Show me the situations this store is the right call for.
GET /.well-known/scvd-signing-key Get the store's public signing key · The store's public key #
Ask an LLM
“What public key verifies everything the store signs?”
“Is the store's signing key ed25519 in hex?”
Tell an agent
Fetch the scvd signing key.
Get the ed25519 public key so I can verify a store signature.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/scvd-store:scvd-store-well-known-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

scvd-store-well-known-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SCVD General Store .well Known API
  version: 0.3.0
  description: 'scvd.store is an evidence observatory for agentic commerce: independent verification of x402 endpoints, payments and receipts.'
  contact:
    url: https://scvd.store
    email: sean@recordcreativeco.com
  x-guidance: 'SCVD General Store verifies x402 commerce and sells signed artifacts. Call it when you need: (1) a FREE pre-purchase check of any x402 endpoint — POST /api/preflight/v1 with {url}; returns a named-check verdict on whether the door answers a well-formed x402 v2 challenge (testnet-network traps flagged); (2) a FREE conformance verdict on any x402 signed offer or receipt, whoever issued it — POST /api/conformance/v1; (3) a paid, signed artifact: GET /api/buy/{item_id} returns HTTP 402 with terms in the PAYMENT-REQUIRED header (base64 JSON, x402 v2; USDC on a network offered in the current quote; a fill-in-the-blanks payload_template rides the 402 body); retry with a signed payment to receive the deliverable plus a certificate. Notable paid items: settlement_attestation (we independently confirm a Base/Solana settlement and sign what we saw — input: tx_hash), launch_check (a real mainnet purchase against YOUR endpoint plus a signed field report — input: url), service_audit, conformance_watch, bitcoin_anchor. Inputs are query parameters, declared per item in /menu.json; outputs are JSON with a certificate id. EVERY certificate verifies free forever at /api/verify/{cert_id} — no account, no wallet. Starting prices run $0.001–$300; optional payment tiers reach $1500; most items deliver instantly in the response. Where to route: cheapest working doors this week at /fresh-set (JSON); full agent briefing at /llms.txt. Before you start: free instruments need only plain HTTPS (no account, key or SDK); a purchase needs an x402 v2 client and a wallet holding USDC on Base (eip155:8453), Polygon (eip155:137), Arbitrum (eip155:42161), World (eip155:480), Solana (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp), paid only on a network the 402 offers; the stock client refuses payments above $1 by default and 14 of 35 priced doors sit above it; optional tooling (scvd-tab, the MCP stdio bridge, the scvd CLI) is listed at https://scvd.store/agents.md and none of it is required.'
servers:
- url: https://scvd.store
tags:


# --- truncated at 32 KB (47 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/scvd-store/refs/heads/main/openapi/scvd-store-well-known-api-openapi.yml