SCVD General Store · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for SCVD General Store .well Known API

12 actions 12 updates phrasing extends openapi/scvd-store-well-known-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for SCVD General Store's API. It is a proposal applied on top of the contract, not a document SCVD General Store publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 12

$.info
$.paths['/.well-known/oauth-protected-resource'].get
$.paths['/.well-known/api-catalog'].get
$.paths['/.well-known/ard.json'].get
$.paths['/.well-known/ai-catalog.json'].get
$.paths['/.well-known/mcp.json'].get
$.paths['/.well-known/http-message-signatures-directory'].get
$.paths['/.well-known/x402'].get
$.paths['/.well-known/x402.json'].get
$.paths['/.well-known/mcp'].get
$.paths['/.well-known/agent-instructions'].get
$.paths['/.well-known/scvd-signing-key'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for SCVD General Store .well Known API
  version: 1.0.0
extends: openapi/scvd-store-well-known-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 11
- target: $.paths['/.well-known/oauth-protected-resource'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the protected-resource metadata
      effect: read
      questions:
      - Does this store publish RFC 9728 protected-resource metadata?
      - Is there an OAuth authorization server gating the store's resources?
      instructions:
      - text: Fetch the store's OAuth protected-resource metadata.
      - text: Show me what gates this resource according to RFC 9728.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/api-catalog'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the RFC 9727 API catalog
      effect: read
      questions:
      - Which API surfaces does this origin serve, as an RFC 9727 linkset?
      - Where is each API's OpenAPI contract and status link listed?
      instructions:
      - text: Get the store's API catalog.
      - text: List every API surface and its service-desc link from the api-catalog.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/ard.json'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the Agentic Resource Discovery manifest
      effect: read
      questions:
      - 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?
      instructions:
      - text: Fetch ard.json.
      - text: Show me the agentic resource discovery entries this origin publishes.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/ai-catalog.json'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the ARD manifest at its predecessor path
      effect: read
      questions:
      - 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?
      instructions:
      - text: Fetch the legacy ai-catalog.json manifest.
      - text: Read the predecessor-path copy of the ARD manifest.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/mcp.json'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the MCP manifest at the .json alias
      effect: read
      questions:
      - Is the MCP manifest also available at mcp.json?
      - Which scanners need the .json alias of the MCP manifest?
      instructions:
      - text: Fetch /.well-known/mcp.json.
      - text: Read the MCP server manifest from its .json alias.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/http-message-signatures-directory'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the store's Web Bot Auth key directory
      effect: read
      questions:
      - 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?
      instructions:
      - text: Fetch the store's http-message-signatures directory.
      - text: Get the key set the store uses to sign its probes.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/x402'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the minimal x402 discovery listing
      effect: read
      questions:
      - What is the de-facto x402 indexer entry point for this store?
      - Which priced resources does the minimal x402 discovery file list?
      instructions:
      - text: Fetch /.well-known/x402.
      - text: Read the store's minimal x402 discovery document.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/x402.json'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the full x402 catalog of payable resources
      effect: read
      questions:
      - Where is the richer origin-hosted catalog of payable x402 resources?
      - Does x402.json carry more detail than the minimal discovery file?
      instructions:
      - text: Fetch /.well-known/x402.json.
      - text: Get the full x402 catalog with every payable resource.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/mcp'].get
  update:
    x-apievangelist-phrasing:
      intent: Find where the MCP server is
      effect: read
      questions:
      - Where is the store's MCP endpoint and which protocol versions does it negotiate?
      - Which MCP methods answer without payment?
      instructions:
      - text: Fetch /.well-known/mcp.
      - text: Tell me the MCP endpoint, its capabilities and the initialize request to send.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/agent-instructions'].get
  update:
    x-apievangelist-phrasing:
      intent: Read when an agent should use this store
      effect: read
      questions:
      - 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?
      instructions:
      - text: Fetch the store's agent instructions.
      - text: Show me the situations this store is the right call for.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/.well-known/scvd-signing-key'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the store's public signing key
      effect: read
      questions:
      - What public key verifies everything the store signs?
      - Is the store's signing key ed25519 in hex?
      instructions:
      - text: Fetch the scvd signing key.
      - text: Get the ed25519 public key so I can verify a store signature.
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/scvd-store-well-known-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.