Agentic Web Wiki — standards reference, probe, validate, template

Define a glossary term of the agentic web. Input: term (id, name or alias; plurals tolerated). Returns the definition and related protocol ids. If the word is the name of a standard rather than a term (x402, ARD, AGENTS.md) it returns that standard's summary instead of an error.

{
  "type": "object",
  "properties": {
    "term": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80
    }
  },
  "required": [
    "term"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Get one standard's full record by id: status, governance, version, spec URL, discovery, probe rule, evidence with URLs, disputes, summary, freshness. The id may be written as the file or path it is known by (llms.txt, /.well-known/ard.json, A2A); a miss names the nearest ids.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Search the standards by name, acronym, alias, question or use case. Input: q (plain words are fine: 'A2A vs MCP', 'pay per request'). Returns up to 10 matches with id, step and status; a word that is a standard's id or acronym ranks first, and acronym clashes such as ACP are all returned.

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "minLength": 2,
      "maxLength": 200
    }
  },
  "required": [
    "q"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Check one public origin for one standard by fetching its well-known path live. Input: origin (hostname), id (standard id). Returns found/absent with the URL, status and reason; an apex that redirects to its www. host is followed and reported as final_origin.

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "minLength": 1,
      "maxLength": 253
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120
    }
  },
  "required": [
    "origin",
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Check one public origin for every standard that can be observed without credentials (about 30 GET rules). Input: origin. Returns found, absent and skipped (with reasons) plus coverage by lifecycle step. An apex that redirects to its www. host is followed and reported as final_origin.

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "minLength": 1,
      "maxLength": 253
    }
  },
  "required": [
    "origin"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

What changed on the map since a date. Input: since (YYYY-MM-DD; an ISO-8601 timestamp is cut to its date), optional step, record_id, limit. Returns dated rows with record, kind, field, old and new value, claim, evidence URL and the data commit.

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "minLength": 10,
      "maxLength": 40,
      "description": "YYYY-MM-DD, or an ISO-8601 timestamp (its offset is applied, then the UTC date is used)"
    },
    "step": {
      "type": "string",
      "maxLength": 40
    },
    "record_id": {
      "type": "string",
      "maxLength": 80
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "required": [
    "since"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Records whose last verification is older than N days (default 30), optionally within one lifecycle step. Returns the matching records (id, name, step, last_verified, freshness) and, always, total_standards, cutoff, oldest_verified and newest_verified so an empty list is still informative.

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 3650
    },
    "step": {
      "type": "string",
      "maxLength": 40
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Validate a public origin's agent-facing manifests against their specifications and grade its agentic-web readiness. Input: origin; optional id to check one manifest only (ard, ai-catalog-well-known-file, mcp-server-cards, a2a, llms-txt, agents-md, api-catalog-rfc9727, ai-crawler-tokens-robots, security-txt, auth-md). Returns grade A+ to F with the rubric, per-manifest errors (spec violations) and warnings (best practice), steps covered, what an agent can call, and the cheapest next steps. The same report is a page at /check/<domain>/ with a badge at /badge/<domain>.svg.

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "minLength": 1,
      "maxLength": 253
    },
    "id": {
      "type": "string",
      "enum": [
        "ard",
        "ai-catalog-well-known-file",
        "mcp-server-cards",
        "a2a",
        "llms-txt",
        "agents-md",
        "api-catalog-rfc9727",
        "ai-crawler-tokens-robots",
        "security-txt",
        "auth-md"
      ]
    }
  },
  "required": [
    "origin"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Spec-compliant boilerplate for an agent-facing file, filled with your domain: ard (and ai-catalog-well-known-file), llms-txt, agents-md, mcp-server-cards (SEP-2127), a2a (agent card 1.0), ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md. Input: id; optional domain, name, description, mcp_url, api_url, agent_url, contact. Returns target_path, content_type, recommended_headers, contents, the fields to edit, notes on the specification, and the validate_manifest call to run once it is live.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 2,
      "maxLength": 60,
      "description": "one of ard, ai-catalog-well-known-file, llms-txt, agents-md, mcp-server-cards, a2a, ai-crawler-tokens-robots, api-catalog-rfc9727, security-txt, auth-md"
    },
    "domain": {
      "description": "bare hostname the file is for, e.g. example.com (default example.com)",
      "type": "string",
      "maxLength": 253
    },
    "name": {
      "type": "string",
      "maxLength": 100
    },
    "description": {
      "type": "string",
      "maxLength": 300
    },
    "mcp_url": {
      "description": "absolute https URL of the MCP endpoint",
      "type": "string",
      "maxLength": 200
    },
    "api_url": {
      "description": "absolute https URL of the OpenAPI description",
      "type": "string",
      "maxLength": 200
    },
    "agent_url": {
      "description": "absolute https URL of the A2A endpoint",
      "type": "string",
      "maxLength": 200
    },
    "contact": {
      "description": "mailto:, https: or tel: URI (a bare email gets mailto:)",
      "type": "string",
      "maxLength": 200
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Ask what to implement for a goal in plain words, e.g. 'let agents pay per request', 'stop AI training crawls', 'let ChatGPT call my API'. Input: question; optional use_case (one of the 15 use-case ids in the schema) and audience. Returns the matched use case(s), up to 8 standards ranked by fit, maturity and adoption with reasons, do_this_first (prerequisites first), deprecated standards to avoid, and related ones to consider (also_consider carries id, name, step and question).

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "minLength": 3,
      "maxLength": 200
    },
    "use_case": {
      "type": "string",
      "enum": [
        "discover-my-api",
        "expose-tools-to-agents",
        "let-agents-act-on-my-site",
        "serve-content-to-agents",
        "prove-agent-identity",
        "delegate-user-authority",
        "control-ai-crawling",
        "accept-agent-payments",
        "agent-checkout",
        "agent-to-agent-messaging",
        "agent-naming",
        "render-agent-ui",
        "audit-agent-actions",
        "attribute-agent-traffic",
        "describe-agent-capabilities"
      ]
    },
    "audience": {
      "type": "string",
      "enum": [
        "site-owner",
        "agent-builder",
        "platform",
        "standards-body"
      ]
    }
  },
  "required": [
    "question"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The agentic-web daily digest as structured data. Input: date (YYYY-MM-DD, default latest), or list: true for the index of every published date. Returns headline, lede, items (title, body, why_it_matters, kind, related standards, and the sources each item rests on, labelled VERIFIED or REPORTED), the day's measured stats (adoption and grade changes across a fixed panel of domains re-checked daily, fastest-growing repositories, MCP Registry activity) and how it was made. Every number in an item appears in a source it cites. Human version: https://agenticweb.wiki/digest/.

{
  "type": "object",
  "properties": {
    "date": {
      "description": "YYYY-MM-DD or latest (default)",
      "type": "string",
      "maxLength": 40
    },
    "list": {
      "description": "true: the index of published dates instead of one digest",
      "type": "boolean"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}