{ "generated": "2026-10-30", "url": "https://agenticweb.wiki/data/versions.json", "changes_url": "https://agenticweb.wiki/data/changes.json", "count": 132, "manifests": { "ard": { "id": "ard", "name": "Agentic Resource Discovery (ARD)", "current_version": "0.91", "schema_spec_version": "1.0", "version_date": "2026-08-29", "canonical_path": "/.well-known/ard.json", "accepted_paths": [ "/.well-known/ard.json" ], "deprecated_paths": [ { "path": "/.well-known/ai-catalog.json", "deprecated_since": "2026-08-29", "superseded_by": "/.well-known/ard.json", "reason": "ARD v0.91 renamed /.well-known/ai-catalog.json to /.well-known/ard.json" } ], "legacy_shapes": [ { "pattern": "only /.well-known/ai-catalog.json served", "status": "valid_legacy", "note": "Serve /.well-known/ard.json (and mirror at /.well-known/ai-catalog.json during migration)" } ], "content_type": "application/ai-catalog+json", "schema_url": "https://raw.githubusercontent.com/ards-project/ard-spec/main/spec/schemas/ai-catalog.schema.json", "required_fields": [ "specVersion", "entries[].identifier", "entries[].type", "entries[].url|data" ] }, "ai-catalog-well-known-file": { "id": "ai-catalog-well-known-file", "name": "AI Catalog well-known file (ARD predecessor & SEP-2127 catalog path)", "current_version": "1.0", "version_date": "2026-10-06", "canonical_path": "/.well-known/ard.json", "accepted_paths": [ "/.well-known/ai-catalog.json" ], "deprecated_paths": [ { "path": "/.well-known/ai-catalog.json", "deprecated_since": "2026-08-29", "superseded_by": "/.well-known/ard.json", "reason": "Renamed to /.well-known/ard.json in ARD v0.91; still referenced by MCP SEP-2127 domain discovery" } ], "legacy_shapes": [ { "pattern": "/.well-known/ai-catalog.json without /.well-known/ard.json", "status": "valid_legacy", "note": "Valid SEP-2127/pre-ARD catalog path; serve /.well-known/ard.json alongside it for ARD v0.91+ clients" } ], "content_type": "application/ai-catalog+json", "schema_url": "https://raw.githubusercontent.com/ards-project/ard-spec/main/spec/schemas/ai-catalog.schema.json", "required_fields": [ "specVersion", "entries[].identifier", "entries[].type", "entries[].url|data" ] }, "mcp-server-cards": { "id": "mcp-server-cards", "name": "MCP Server Cards (SEP-2127)", "current_version": "2026-10-06", "schema_spec_version": "v1", "version_date": "2026-10-06", "canonical_path": "/mcp/server-card", "accepted_paths": [ "/mcp/server-card", "/.well-known/mcp/server-card.json" ], "deprecated_paths": [ { "path": "/.well-known/mcp.json", "deprecated_since": "2026-10-06", "superseded_by": "/mcp/server-card", "reason": "SEP-1649 /.well-known/mcp.json superseded by SEP-2127 /server-card and /.well-known/mcp/server-card.json" } ], "legacy_shapes": [ { "pattern": "top-level url/transport/tools or serverInfo without $schema and remotes[]", "status": "valid_legacy", "note": "Pre-final SEP-2127 draft shape; final SEP-2127 requires $schema, reverse-DNS name, version, description, and remotes[]" }, { "pattern": "top-level mcpServers map", "status": "absent", "note": "Client-config map (Cursor/Claude Desktop shape), not a server card" } ], "content_type": "application/mcp-server-card+json", "schema_url": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json", "required_fields": [ "$schema", "name", "version", "description", "remotes[].type", "remotes[].url" ] }, "a2a": { "id": "a2a", "name": "Agent2Agent Protocol (A2A) Agent Card", "current_version": "1.0", "version_date": "2026-07-01", "canonical_path": "/.well-known/agent-card.json", "accepted_paths": [ "/.well-known/agent-card.json" ], "deprecated_paths": [ { "path": "/.well-known/agent.json", "deprecated_since": "2025-07-30", "superseded_by": "/.well-known/agent-card.json", "reason": "A2A v0.3+ renamed /.well-known/agent.json to /.well-known/agent-card.json" } ], "legacy_shapes": [ { "pattern": "protocolVersion 0.x or missing supportedInterfaces[]", "status": "valid_legacy", "note": "A2A 0.2/0.3 shape uses top-level url; A2A 1.0 declares interfaces in supportedInterfaces[] ({url, protocolBinding, protocolVersion})" }, { "pattern": "url pointing to HTML homepage (e.g. Mintlify docs template)", "status": "pseudo_endpoint_html", "note": "Card metadata is present but url points to human HTML documentation rather than a callable A2A endpoint" } ], "content_type": "application/json", "schema_url": "https://github.com/a2aproject/A2A", "required_fields": [ "name", "description", "version", "supportedInterfaces[].url", "supportedInterfaces[].protocolBinding", "supportedInterfaces[].protocolVersion", "skills[].id", "skills[].name", "skills[].description", "skills[].tags" ] }, "llms-txt": { "id": "llms-txt", "name": "llms.txt", "current_version": "2024-09-03", "version_date": "2024-09-03", "canonical_path": "/llms.txt", "accepted_paths": [ "/llms.txt", "/llms-full.txt" ], "deprecated_paths": [], "legacy_shapes": [], "content_type": "text/markdown", "schema_url": "https://llmstxt.org/", "required_fields": [ "# H1 Title", "> Blockquote summary", "Markdown links" ] }, "agents-md": { "id": "agents-md", "name": "AGENTS.md", "current_version": "1.0", "version_date": "2025-08-20", "canonical_path": "/AGENTS.md", "accepted_paths": [ "/AGENTS.md" ], "deprecated_paths": [], "legacy_shapes": [], "content_type": "text/markdown", "schema_url": "https://agents.md/", "required_fields": [ "Markdown heading (# ...)" ] }, "anthropic-agent-skills-format": { "id": "anthropic-agent-skills-format", "name": "Agent Skills Discovery", "current_version": "0.2.0", "version_date": "2026-03-01", "canonical_path": "/.well-known/agent-skills/index.json", "accepted_paths": [ "/.well-known/agent-skills/index.json" ], "deprecated_paths": [], "legacy_shapes": [], "content_type": "application/json", "schema_url": "https://schemas.agentskills.io/discovery/0.2.0/schema.json", "required_fields": [ "$schema", "skills[].name", "skills[].description", "skills[].url", "skills[].digest" ] }, "api-catalog-rfc9727": { "id": "api-catalog-rfc9727", "name": "api-catalog (RFC 9727)", "current_version": "RFC 9727", "version_date": "2025-06-01", "canonical_path": "/.well-known/api-catalog", "accepted_paths": [ "/.well-known/api-catalog" ], "deprecated_paths": [], "legacy_shapes": [ { "pattern": "Content-Type application/json instead of application/linkset+json", "status": "valid_legacy", "note": "RFC 9727 §4 requires application/linkset+json (RFC 9264)" } ], "content_type": "application/linkset+json", "schema_url": "https://www.rfc-editor.org/rfc/rfc9727", "required_fields": [ "linkset[].anchor", "linkset[].service-desc|service-doc|service-meta|item" ] }, "ai-crawler-tokens-robots": { "id": "ai-crawler-tokens-robots", "name": "AI Crawler User-Agent Tokens in robots.txt", "current_version": "RFC 9309 + AI Tokens", "version_date": "2026-10-01", "canonical_path": "/robots.txt", "accepted_paths": [ "/robots.txt" ], "deprecated_paths": [], "legacy_shapes": [ { "pattern": "anthropic-ai or Claude-Web user-agent tokens", "status": "valid_legacy", "note": "Retired by Anthropic in favour of ClaudeBot, Claude-SearchBot, and Claude-User" } ], "content_type": "text/plain", "schema_url": "https://www.rfc-editor.org/rfc/rfc9309", "required_fields": [ "User-agent", "Allow|Disallow|Content-Signal|Agentmap" ] }, "security-txt": { "id": "security-txt", "name": "security.txt (RFC 9116)", "current_version": "RFC 9116", "version_date": "2022-04-01", "canonical_path": "/.well-known/security.txt", "accepted_paths": [ "/.well-known/security.txt" ], "deprecated_paths": [ { "path": "/security.txt", "deprecated_since": "2022-04-01", "superseded_by": "/.well-known/security.txt", "reason": "RFC 9116 §3 prefers /.well-known/security.txt" } ], "legacy_shapes": [], "content_type": "text/plain", "schema_url": "https://www.rfc-editor.org/rfc/rfc9116", "required_fields": [ "Contact", "Expires" ] }, "auth-md": { "id": "auth-md", "name": "auth.md", "current_version": "0.1", "version_date": "2026-04-01", "canonical_path": "/auth.md", "accepted_paths": [ "/auth.md" ], "deprecated_paths": [], "legacy_shapes": [], "content_type": "text/markdown", "schema_url": "https://agenticweb.wiki/protocols/auth-md/", "required_fields": [ "identity_assertion|service_auth|anonymous" ] }, "okf": { "id": "okf", "name": "Open Knowledge Format (OKF)", "current_version": "0.2", "version_date": "2026-09-01", "canonical_path": "/okf/index.md", "accepted_paths": [ "/okf/index.md" ], "deprecated_paths": [], "legacy_shapes": [ { "pattern": "okf_version: 0.1", "status": "valid_legacy", "note": "OKF 0.2 adds structured knowledge-graph frontmatter" } ], "content_type": "text/markdown", "schema_url": "https://agenticweb.wiki/protocols/okf/", "required_fields": [ "okf_version (0.1 or 0.2)", "Markdown concept links" ] } }, "standards": { "mcp": { "id": "mcp", "name": "Model Context Protocol", "acronym": "MCP", "step": "act", "phase": "living", "native_status": "Active open protocol. 2026-07-28 is the current revision [2]. Code and specifications are released under the Apache License 2.0 [10]", "current_version": "2026-07-28", "version_date": "2026-07-28", "canonical_path": "No fixed path. A local server is launched by the client as a subprocess over stdio [7]. A remote server exposes one Streamable HTTP endpoint at a URL its operator publishes, for example https://mcp.linear.app/mcp [6][18]. Optional discovery: a Server Card at /server-card (SEP-2127, Final) [8], and the official MCP Registry, which is in preview [9]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "MCP endpoints are not at a fixed well-known path. On 2026-07-28, capabilities are read with server/discover; initialize is the legacy handshake for 2025-11-25 and earlier. The server card is GET /server-card." }, "spec_url": "https://modelcontextprotocol.io/specification/2026-07-28", "last_verified": "2026-10-28", "freshness": "current" }, "a2a": { "id": "a2a", "name": "Agent2Agent Protocol (A2A)", "acronym": "A2A", "step": "coordinate", "phase": "stable", "native_status": "Stable: v1.0 is \"the first stable specification\" [9]", "current_version": "1.0.1", "version_date": "2026-05-28", "canonical_path": "/.well-known/agent-card.json", "deprecated_paths": [ "/.well-known/agent.json" ], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent-card.json", "expect": { "content_type": "json", "json_keys": [ "name" ], "text_match": "\"url\"\\s*:|supportedInterfaces" }, "note": "An A2A Agent Card names the agent and where to reach it: a top-level url on a 0.3 card, or url, protocolBinding, and protocolVersion inside supportedInterfaces on a 1.0 card." }, "spec_url": "https://a2a-protocol.org/latest/specification/", "last_verified": "2026-10-28", "freshness": "current" }, "agent-client-protocol": { "id": "agent-client-protocol", "name": "Agent Client Protocol", "acronym": "ACP", "step": "act", "phase": "stable", "native_status": "Active. Protocol version 1 is stable [16]; v2 has been published in Draft form since 2026-07-20 [13]. Remote-agent support is \"a work in progress\" [7]", "current_version": "1 (Rust crate v1.13.0, JSON Schema v1.27.0)", "version_date": "2026-10-27", "canonical_path": "No fixed URL. A local agent is launched by the client as a subprocess and talks over stdin and stdout [9]. Agents can be found through the ACP Registry, a curated list of agents that support authentication, whose index is https://cdn.agentclientprotocol.com/registry/v1/latest/registry.json [19][21]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "client-side", "note": "ACP runs between an editor and a local agent binary over stdio." }, "spec_url": "https://agentclientprotocol.com/protocol/v1/overview", "last_verified": "2026-10-28", "freshness": "current" }, "agent-communication-protocol": { "id": "agent-communication-protocol", "name": "Agent Communication Protocol", "acronym": "ACP", "step": "coordinate", "phase": "deprecated", "native_status": "\"ACP is now part of A2A under the Linux Foundation\" (repository banner)", "current_version": "v1.0.3", "version_date": "2025-08-21", "canonical_path": "/agents", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "superseded", "note": "IBM ACP was archived and merged into A2A; /agents is not expected on new deployments." }, "spec_url": "https://github.com/i-am-bee/acp", "last_verified": "2026-10-23", "freshness": "current" }, "agentic-commerce-protocol": { "id": "agentic-commerce-protocol", "name": "Agentic Commerce Protocol", "acronym": "ACP", "step": "pay", "phase": "living", "native_status": "Beta [5]. The checkout and delegate-payment RFCs are marked Draft, the product-feeds and discovery RFCs Proposal [14][15][16][17]. On 2026-03-24 OpenAI let merchants use their own checkouts in ChatGPT and shifted its ACP use towards product discovery [2]", "current_version": "2026-04-17", "version_date": "2026-04-17", "canonical_path": "GET https://{domain}/.well-known/acp.json, the discovery document added in version 2026-04-17 [13][17]. No site was found serving it: the path returned HTTP 404 on www.etsy.com, www.shopify.com, www.urbanoutfitters.com, www.target.com, www.sephora.com, www.walmart.com, www.nordstrom.com, www.wayfair.com and www.agenticcommerce.dev (checked 2026-10-28)", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /checkout_sessions, which creates a checkout on the merchant; never run unauthenticated." }, "spec_url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol", "last_verified": "2026-10-29", "freshness": "current" }, "ucp": { "id": "ucp", "name": "Universal Commerce Protocol (UCP)", "acronym": "UCP", "step": "pay", "phase": "living", "native_status": "Live. Dated releases since 2026-01-11; ucp.dev also publishes a \"draft\" version [11], which on 2026-10-28 held the Lodging Booking capability (dev.ucp.lodging.booking), announced as a draft on 2026-09-25 [20][9]", "current_version": "2026-08-25, marked \"latest\" on ucp.dev [11]. Releases on GitHub: v2026-08-25 (published 2026-08-25), v2026-04-08 (published 2026-04-09 UTC), v2026-01-23 (published 2026-01-23) and v2026-01-11 (published on GitHub on 2026-01-23; the announcements page dates the release 2026-01-11) [10][9]", "version_date": "2026-08-25", "canonical_path": "GET /.well-known/ucp on the business's own domain: \"Businesses publish their profile at /.well-known/ucp; platforms publish their profile at the URI advertised in UCP-Agent.\" [12]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/ucp", "expect": { "content_type": "json", "text_match": "\"(ucp|services|capabilities)\"\\s*:\\s*[{\\[]" }, "note": "A UCP profile is a JSON document declaring a ucp block, services, or supported capabilities at /.well-known/ucp." }, "spec_url": "https://ucp.dev/latest/specification/overview/", "last_verified": "2026-10-29", "freshness": "current" }, "ap2": { "id": "ap2", "name": "Agent Payments Protocol (AP2)", "acronym": "AP2", "step": "pay", "phase": "candidate", "native_status": "Pre-1.0. FIDO's September 2026 slides say: \"September 2026: AP2/VI specs moved to public repository for review.\" \"Targeting End 2026: Harmonize AP2 and VI specifications. Mid-2027: Publish first version of consolidated specifications.\" The dates after September 2026 are targets [4]", "current_version": "v0.2.0", "version_date": "2026-04-28", "canonical_path": "No well-known file. Under the v0.1 A2A extension an agent lists AP2 in its A2A Agent Card extensions with the URI https://github.com/google-agentic-commerce/ap2/tree/v0.1 [15]. That URI is an identifier: fetched as a web page it returned HTTP 404 on 2026-10-28. No v0.2 discovery URI was found", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "AP2 mandates are exchanged inside an authorised checkout; nothing is published at a fixed path." }, "spec_url": "https://ap2-protocol.org/ap2/specification/", "last_verified": "2026-10-29", "freshness": "current" }, "ap2-checkout-mandate": { "id": "ap2-checkout-mandate", "name": "AP2 Checkout Mandate", "acronym": null, "step": "pay", "phase": "withdrawn", "native_status": "AP2 specification component, not an independently published protocol", "current_version": "v0.2.0", "version_date": "2026-04-28", "canonical_path": "none", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "A component of AP2, observable only inside a checkout." }, "spec_url": "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/checkout_mandate.md", "last_verified": "2026-10-23", "freshness": "current" }, "x402": { "id": "x402", "name": "x402", "acronym": null, "step": "pay", "phase": "living", "native_status": "In production use; the Foundation calls it \"an open, neutral standard for internet-native payments\" [6]", "current_version": "2.0", "version_date": "2025-12-09", "canonical_path": "No fixed path: a resource signals x402 per request by answering HTTP 402 [11]. Discovery is through the Bazaar, a /discovery/resources listing that facilitators may offer [9][18]; Coinbase's is public at https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources (checked 2026-10-28)", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "A 402 challenge appears only on a URL that charges; there is no fixed path to check." }, "spec_url": "https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md", "last_verified": "2026-10-29", "freshness": "current" }, "l402": { "id": "l402", "name": "L402", "acronym": "L402", "step": "pay", "phase": "living", "native_status": "In production use: Lightning Labs said in 2020 that Aperture was \"used in production today by Lightning Loop\" [11]. The bLIP header reads \"bLIP: 26 Title: L402: The Lightning HTTP 402 Protocol Status: Active\" [7] although the PR is not merged [6]", "current_version": "No numbered release", "version_date": null, "canonical_path": "No fixed path: a resource signals L402 per request by answering HTTP 402 with an L402 WWW-Authenticate challenge [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "L402 challenges appear only on paid URLs." }, "spec_url": "https://raw.githubusercontent.com/lightninglabs/L402/master/protocol-specification.md", "last_verified": "2026-10-29", "freshness": "current" }, "mpp": { "id": "mpp", "name": "Machine Payments Protocol (MPP)", "acronym": "MPP", "step": "pay", "phase": "review", "native_status": "\"Document Type Active Internet-Draft (individual)\", \"Last updated 2026-09-09\", \"IESG state I-D Exists\" [8]. In production use: payment methods are in production [3], and five services checked live on 2026-10-29 answered with MPP challenges (see Who uses it)", "current_version": "draft-httpauth-payment-01", "version_date": "2026-09-09", "canonical_path": "No fixed path: a resource signals MPP per request by answering HTTP 402 with a WWW-Authenticate: Payment challenge [5][9]. Services can also be listed in the curated mpp.dev/services directory (https://mpp.dev/api/services listed 138 services on 2026-10-29 [23][34]) or self-registered on MPPScan (by Merit Systems) [35]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "MPP challenges appear only on paid URLs." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-httpauth-payment-01", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8004": { "id": "erc-8004", "name": "ERC-8004: Trustless Agents", "acronym": "ERC-8004", "step": "identify", "phase": "draft", "native_status": "`status: Draft` in the canonical EIP repository (created `2025-08-13`; PR `#1170` merged `2025-08-18`; moved to `Review` in commit `cb7ae283` on `2025-10-08`; returned to `Draft` in commit `acf085cb` / PR `#1470` on `2026-01-13`; latest specification commit `503591a6` on `2026-01-25`) [1][2][3][4]", "current_version": "Draft ERC, created 2025-08-13; Identity and Reputation Registries live on Ethereum mainnet since 2026-01-29", "version_date": "2025-08-13", "canonical_path": "/.well-known/agent-registration.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent-registration.json", "expect": { "content_type": "json", "json_keys": [ "registrations" ] }, "note": "ERC-8004 agents publish a registration file with a top-level registrations[] array at the domain they claim." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8004", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8183": { "id": "erc-8183", "name": "ERC-8183: Agentic Commerce", "acronym": "ERC-8183", "step": "pay", "phase": "draft", "native_status": "Draft ERC — 'This specification defines the Agentic Commerce Protocol: a job with escrowed budget...'", "current_version": "Draft, created 2026-02-25", "version_date": "2026-02-25", "canonical_path": "none — no well-known file; discovery is by contract address/ABI", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "An Ethereum contract; observable via eth_call, not HTTP." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8183", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8226": { "id": "erc-8226", "name": "ERC-8226 Regulated Agent Mandate", "acronym": "ERC-8226", "step": "permit", "phase": "draft", "native_status": "Draft, Standards Track: ERC (marked ⚠️ Draft on eips.ethereum.org)", "current_version": "Draft, created 2026-04-12", "version_date": "2026-04-12", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "An Ethereum contract; observable via eth_call, not HTTP." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8226", "last_verified": "2026-10-29", "freshness": "current" }, "webmcp": { "id": "webmcp", "name": "WebMCP", "acronym": null, "step": "act", "phase": "draft", "native_status": "Draft Community Group Report [1]. Chrome: early preview from 2026-02-10 [14]; origin trial in Chrome 149 to 156, with shipping estimated for Chrome 157 [16][18]. Edge: origin trial from Edge 150, expiring 2027-03-30 [10][19]. Mozilla’s standards position is labelled neutral [22]; WebKit’s is labelled oppose [23]", "current_version": "Draft Community Group Report, 27 October 2026", "version_date": "2026-10-27", "canonical_path": "No file or well-known URL. Tools exist only while a page is open, after its script registers them, so an agent has to load the page to find them. Chrome’s docs: \"Tool discoverability: Clients and browsers must visit a site directly to know if it has callable tools.\" [1][15]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "client-side", "note": "WebMCP is a browser API on the page; observable only by executing the page." }, "spec_url": "https://webmachinelearning.github.io/webmcp/", "last_verified": "2026-10-28", "freshness": "current" }, "nlweb": { "id": "nlweb", "name": "NLWeb", "acronym": "NLWeb", "step": "act", "phase": "draft", "native_status": "Public and open to contributions; the code is framed as a demonstration: \"NLWeb provides practical implementation code—not as the definitive solution, but as proof-of-concept demonstrations showing one possible approach.\" [3]. The latest commit on main is dated 2026-06-10 [27]. A path-traversal flaw in the reference server was reported in August 2025: \"What's worse is that it's a classic path traversal flaw, meaning it's as easy to exploit as visiting a malformed URL.\" [25]; a later review notes \"A release note in docs/release_notes lists a fix for a \"path traversal vulnerability in static file handler\" (PR #231)\" and \"When we queried the repository's GitHub security advisories on 24 October 2026, none were published.\" [24]", "current_version": "NLWeb Specification v0.55", "version_date": "2026-03-23", "canonical_path": "No standard discovery path. The specification's HTTP binding is \"POST /ask — Submit a natural language query. POST /await — Check on or cancel a promised result.\" [9]; it is \"NLWeb is designed to be transport-protocol agnostic.\" and \"NLWeb operations can be exposed as Tools within the Model Context Protocol (MCP) or other JSON-RPC-based agentic standards.\" [9]. Paths vary by deployment: the reference server and Cloudflare's Worker use /ask and /mcp [4][12]; Wix uses \"Use the following MCP URL to connect to your favorite AI agent (e.g. Claude, ChatGPT or custom agents): https://www.[your-domain.com]/_api/nlweb/mcp.\" [15]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /ask with a question body; not run from a public tool." }, "spec_url": "https://raw.githubusercontent.com/nlweb-ai/website/main/NLWEBSPEC.md", "last_verified": "2026-10-29", "freshness": "current" }, "anthropic-agent-skills-format": { "id": "anthropic-agent-skills-format", "name": "Agent Skills", "acronym": null, "step": "act", "phase": "living", "native_status": "Published as an open standard on 2025-12-18 [4][6]; spec site and repository agentskills/agentskills since 2025-12-16 [3]; AAIF project since 2026-10-22 [8]. Anthropic proposed a first AAIF roadmap of versioned releases, a formal proposal process and security guidance [7]", "current_version": "unversioned", "version_date": null, "canonical_path": "/.well-known/agent-skills/index.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent-skills/index.json", "expect": { "content_type": "json", "json_keys": [ "skills" ] }, "note": "Agent Skills Discovery RFC v0.2.0 publishes a JSON skill index with a top-level skills[] array at /.well-known/agent-skills/index.json." }, "spec_url": "https://agentskills.io/specification", "last_verified": "2026-10-28", "freshness": "current" }, "llms-txt": { "id": "llms-txt", "name": "llms.txt", "acronym": null, "step": "read", "phase": "draft", "native_status": "Community proposal (v2), not standards-track", "current_version": "v2", "version_date": "2026-08-10", "canonical_path": "/llms.txt", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/llms.txt", "expect": { "text_match": "(?m)^# \\S" }, "note": "llms.txt must begin with an H1 line." }, "spec_url": "https://llmstxt.org", "last_verified": "2026-10-28", "freshness": "current" }, "agents-md": { "id": "agents-md", "name": "AGENTS.md", "acronym": null, "step": "read", "phase": "living", "native_status": "Open format stewarded by the AAIF; not standards-track", "current_version": "No numbered versions published", "version_date": "", "canonical_path": "/AGENTS.md", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/AGENTS.md", "expect": { "text_match": "(?m)^#{1,6}\\s+\\S" }, "note": "AGENTS.md is a Markdown briefing at /AGENTS.md; at least one Markdown heading (# ...) is required so plain-text error stubs do not match." }, "spec_url": "https://agents.md/", "last_verified": "2026-10-28", "freshness": "current" }, "aipref-content-usage-attachment": { "id": "aipref-content-usage-attachment", "name": "AIPREF Content-Usage Attachment", "acronym": "AIPREF", "step": "permit", "phase": "working-group", "native_status": "Active Internet-Draft, not an RFC: \"Document Type Active Internet-Draft (aipref WG) Authors Gary Illyes, Martin Thomson Last updated 2026-08-18 Replaces draft-it-aipref-attachment\" \"IESG state I-D Exists\" [2]. The Datatracker API lists no aipref RFC (checked 2026-10-29) [6]. Working-group last call on -03 began on 2025-09-04 (\"This message starts a 2-week WG Last Call for this document.\") and the draft went back to WG Document on 2025-11-03 [14][3]; the chairs wrote: \"The response was not one we anticipated: several participants raised fundamental issues about the nature of the Internet-Drafts (I-Ds), forcing the group to reconsider its approach.\" [15]. -04 lapsed (\"Expires: 1 May 2026\" [16]; \"2026-05-01 04 (System) Document has expired\" [3]) and -05 renewed it: \"2026-08-18 05 Martin Thomson New version available: draft-ietf-aipref-attach-05.txt\" [3]. The charter milestone was \"2026-08-31 Aug 2026 Standard track protocol specification(s) to associate the AI-related preferences to the IESG for publication draft-ietf-aipref-attach\" [7], moved from August 2025 on 2025-09-23 [8]; on 2026-10-29 the Datatracker still showed the IESG state \"I-D Exists\" [2]. The Content-Usage header field is requested as permanent (\"Field Name: Content-Usage Status: permanent Structured Type: Dictionary\") [1] but was not in the IANA HTTP Field Name registry on 2026-10-29 [23]", "current_version": "draft-ietf-aipref-attach-05", "version_date": "2026-08-19", "canonical_path": "/robots.txt", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/robots.txt", "expect": { "text_match": "(?im)^content-usage:" }, "note": "A Content-Usage line in robots.txt (or HTTP Content-Usage response header on / or /robots.txt) attaches AIPREF preferences to the site." }, "spec_url": "https://www.ietf.org/archive/id/draft-ietf-aipref-attach-05.txt", "last_verified": "2026-10-29", "freshness": "current" }, "aipref-vocabulary": { "id": "aipref-vocabulary", "name": "AIPREF Vocabulary (A Vocabulary For Expressing AI Usage Preferences)", "acronym": "AIPREF", "step": "permit", "phase": "working-group", "native_status": "Active Internet-Draft, not an RFC: \"Document Type Active Internet-Draft (aipref WG) Authors Paul Keller, Martin Thomson\" \"WG state WG Document\" \"IESG state I-D Exists\" [2]. The Datatracker API lists no aipref RFC (checked 2026-10-28) [6]. The document went into working-group last call on 2025-09-04 and back to WG Document on 2025-11-03 [3]: \"Mark Nottingham IETF WG state changed to In WG Last Call from WG Document\"; \"Mark Nottingham IETF WG state changed to WG Document from In WG Last Call\" [3]. The -08 text says \"Its contents DO NOT REFLECT CONSENSUS of the Working Group either in whole or part. Presense or absense of any particular text does not indicate consensus, and this document is published solely as a basis of further discussion.\" [1]. The charter milestone was \"2026-08-31 Aug 2026 A standard track specification describing vocabulary for expressing AI-related preferences to the IESG for publication draft-ietf-aipref-vocab\", moved there on 2025-09-23 from August 2025 [7][8]; on 2026-10-28 the draft had not been sent to the IESG [2]", "current_version": "draft-ietf-aipref-vocab-08", "version_date": "2026-09-14", "canonical_path": "/robots.txt", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/robots.txt", "expect": { "text_match": "(?im)^content-usage:\\s*\\S" }, "note": "Vocabulary tokens are not validated; a non-empty Content-Usage value in robots.txt (or HTTP Content-Usage response header) is the signal." }, "spec_url": "https://www.ietf.org/archive/id/draft-ietf-aipref-vocab-08.txt", "last_verified": "2026-10-28", "freshness": "current" }, "tdmrep": { "id": "tdmrep", "name": "TDMRep (TDM Reservation Protocol)", "acronym": "TDMRep", "step": "permit", "phase": "stable", "native_status": "Final Community Group Report (version 3) [1][4]. The group is still active: its chair posted meeting notes on 2025-10-01 [4], and its TPAC 2025 meeting (2025-11-14) planned to \"discuss a possible evolution of TDMRep, using the Vocabulary defined by AI Pref\" [14]", "current_version": "Version 3", "version_date": "2024-05-10", "canonical_path": "/.well-known/tdmrep.json; tdm-reservation / tdm-policy HTTP headers; in HTML; tdm:reservation in EPUB and PDF metadata [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/tdmrep.json", "expect": { "content_type": "json", "text_match": "tdm-reservation|tdm-policy" }, "note": "A TDMRep file carries tdm-reservation or tdm-policy fields." }, "spec_url": "https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/", "last_verified": "2026-10-29", "freshness": "current" }, "cloudflare-content-signals-policy": { "id": "cloudflare-content-signals-policy", "name": "Content Signals Policy", "acronym": null, "step": "permit", "phase": "living", "native_status": "Live since 2025-09-24 [1]. Cloudflare's own wording is that the signals are preferences, not enforcement: \"It's important to remember that content signals express preferences; they are not technical countermeasures against scraping.\" [1]", "current_version": "No numbered versions", "version_date": "2026-10-22", "canonical_path": "/robots.txt, inside a User-agent group", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/robots.txt", "expect": { "text_match": "(?im)^content-signal:" }, "note": "Content Signals are Content-Signal lines in robots.txt." }, "spec_url": "https://contentsignals.org/", "last_verified": "2026-10-29", "freshness": "current" }, "webbotauth": { "id": "webbotauth", "name": "Web Bot Auth", "acronym": null, "step": "identify", "phase": "working-group", "native_status": "See IETF tracker.", "current_version": "draft-ietf-webbotauth-httpsig-protocol-01", "version_date": "2026-10-29", "canonical_path": "/.well-known/http-message-signatures-directory on the signer's origin, served as application/http-message-signatures-directory+json; the Signature-Agent header tells the site where to look [11]. The draft asks IANA to register the well-known suffix and the media type [11]; on 2026-10-30 neither was yet in the IANA registries [12][28]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/http-message-signatures-directory", "expect": { "content_type": "http-message-signatures-directory", "json_keys": [ "keys" ] }, "note": "A signature directory is a JWKS served with its own media type." }, "spec_url": "https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/", "last_verified": "2026-10-30", "freshness": "current" }, "web-bot-auth-signature-agent-card": { "id": "web-bot-auth-signature-agent-card", "name": "Signature Agent Card (Web Bot Auth registry)", "acronym": null, "step": "identify", "phase": "draft", "native_status": "Active Internet-Draft (`draft-meunier-webbotauth-registry-04`, published 27 October 2026, 26 pages, expires 30 April 2027) [1][2][3][4]", "current_version": "draft-meunier-webbotauth-registry-04", "version_date": "2026-10-27", "canonical_path": "/.well-known/http-message-signatures-directory", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/http-message-signatures-directory", "expect": { "json_keys": [ "client_name" ] }, "note": "The Signature Agent Card adds OAuth client registration fields to the directory." }, "spec_url": "https://www.ietf.org/archive/id/draft-meunier-webbotauth-registry-04.txt", "last_verified": "2026-10-29", "freshness": "current" }, "http-message-signatures": { "id": "http-message-signatures", "name": "HTTP Message Signatures", "acronym": null, "step": "identify", "phase": "stable", "native_status": "Proposed Standard, published February 2024 [3]; IESG approval 2023-08-16 [4]. Two verified errata (verified 2024-10-29) correct \"@signature-input\" to \"@signature-params\" [5][2]", "current_version": "RFC 9421", "version_date": "2024-02", "canonical_path": "No fixed location: the signature travels in the headers of each message. No documentation was found showing that RFC 9421 defines a well-known URI or a key format; an application usually resolves the keyid parameter or uses preregistered keys [1]. Web Bot Auth adds a key directory at /.well-known/http-message-signatures-directory [10]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Signatures appear on individual messages; the webbotauth directory rule covers the published key side." }, "spec_url": "https://www.rfc-editor.org/info/rfc9421/", "last_verified": "2026-10-28", "freshness": "current" }, "ard": { "id": "ard", "name": "Agentic Resource Discovery (ARD)", "acronym": "ARD", "step": "discover", "phase": "draft", "native_status": "\"Proposal\" (the spec’s own label) [1]. The well-known path is not in the IANA Well-Known URIs registry [24], and the spec says its media types are still \"tracking towards formal registration\" [1]", "current_version": "v0.91", "version_date": "2026-08-26", "canonical_path": "/.well-known/ard.json", "deprecated_paths": [ "/.well-known/ai-catalog.json" ], "superseded_by": null, "probe_rule": { "path": "/.well-known/ard.json", "expect": { "json_keys": [ "entries" ] }, "note": "An ARD manifest is JSON with a top-level entries array." }, "spec_url": "https://agenticresourcediscovery.org/spec/", "last_verified": "2026-10-28", "freshness": "current" }, "ai-catalog-well-known-file": { "id": "ai-catalog-well-known-file", "name": "AI Catalog well-known file", "acronym": null, "step": "discover", "phase": "draft", "native_status": "Working draft (specVersion: \"1.0\", published at https://ai-catalog.io/spec/); active domain-level discovery path in MCP Server Cards (SEP-2127, Final 2026-10-06) and optional predecessor path in ARD v0.91 [1][2][20][21][23]", "current_version": "specVersion 1.0 (Working draft)", "version_date": "2026-10-05", "canonical_path": "/.well-known/ard.json", "deprecated_paths": [ "/.well-known/ai-catalog.json" ], "superseded_by": "ard", "probe_rule": { "path": "/.well-known/ai-catalog.json", "expect": { "json_keys": [ "entries" ] }, "note": "Deprecated predecessor path of the ARD manifest, still probed so the census can count migration." }, "spec_url": "https://ai-catalog.io/spec/", "last_verified": "2026-10-29", "freshness": "current" }, "dns-aid": { "id": "dns-aid", "name": "DNS-AID (DNS for AI Discovery)", "acronym": "DNS-AID", "step": "discover", "phase": "draft", "native_status": "Active individual draft, not adopted by a working group. Live records exist on 2 zones found on 2026-10-29, both of them demo or test zones (see \"Who uses it\")", "current_version": "-02", "version_date": "2026-05-27", "canonical_path": "Agent owner names (SVCB), plus the organisation index at `_index._agents.`: \"An SVCB record type query for _index._agents.example.com returns a pointer to an organization-specific registry of all agents.\" [3]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "DNS SVCB records; the HTTP well-known form is covered by the aid rule." }, "spec_url": "https://www.ietf.org/archive/id/draft-mozleywilliams-dnsop-dnsaid-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "ans": { "id": "ans", "name": "Agent Name Service v2 (ANS)", "acronym": "ANS", "step": "identify", "phase": "draft", "native_status": "Active draft. -02 posted \"time\": \"2026-10-26T14:58:32Z\" (07:58 US Pacific, same date) and expires \"expires\": \"2027-04-29T14:58:32Z\" [3][2]. -01 had expired: \"desc\": \"Document has expired\" at \"time\": \"2026-10-15T07:09:06Z\" [4]. GoDaddy calls its service production; its registry page still lists \"Publish Agent (Coming Soon) Manage Agents (Coming Soon)\" [23]", "current_version": "draft-narajala-courtney-ansv2-02", "version_date": "2026-10-26", "canonical_path": "_ans-badge.{agentHost} TXT / _ans.{agentHost} TXT / transparency.ans.godaddy.com", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "The ANS draft defines no fixed well-known path or record type." }, "spec_url": "https://datatracker.ietf.org/doc/draft-narajala-courtney-ansv2/", "last_verified": "2026-10-29", "freshness": "current" }, "aid": { "id": "aid", "name": "Agent Identity & Discovery (AID)", "acronym": "AID", "step": "discover", "phase": "living", "native_status": "\"Date: 2 October 2026 Editor: Agent Community Status: Current normative specification\" [1]. Internet-Drafts: draft-nemethi-dawn-aid-00 (2026-09-02, active) [15][16]; draft-nemethi-aid-agent-identity-discovery-00 (2026-03-16, v1.2, expired) [17][18]", "current_version": "v2.1.1", "version_date": "2026-10-02", "canonical_path": "DNS TXT at _agent., exact host only: \"Clients MUST NOT walk up to parent domains.\" [1]. If DNS fails, clients may fetch /.well-known/agent over HTTPS on the same host [1][2]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent", "expect": { "content_type": "json", "json_keys": [ "uri" ] }, "note": "The AID well-known document mirrors the DNS TXT record, including uri." }, "spec_url": "https://aid.agentcommunity.org/docs/specification", "last_verified": "2026-10-28", "freshness": "current" }, "adp": { "id": "adp", "name": "Agent Discovery Protocol (ADP) v1.1", "acronym": "ADP", "step": "discover", "phase": "draft", "native_status": "\"Active Internet-Draft (individual)\"; \"IESG state I-D Exists\" [2]. \"This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.\" is Datatracker's own wording [2]. The draft says \"Intended status: Informational\" [1]. Datatracker also shows \"RFC stream (None)\" [2].", "current_version": "draft-pro-adp-agent-discovery-02", "version_date": "2026-06-23", "canonical_path": "/.well-known/agent.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent.json", "expect": { "json_keys": [ "identity", "endpoints" ] }, "note": "An ADP agent.json has identity and endpoints blocks." }, "spec_url": "https://www.ietf.org/archive/id/draft-pro-adp-agent-discovery-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "ardp": { "id": "ardp", "name": "Agent Registration and Discovery Protocol", "acronym": "ARDP", "step": "discover", "phase": "deprecated", "native_status": "Expired Internet-Draft (expired 2026-08-28)", "current_version": "draft-pioli-agent-discovery-01 (latest revision, expired)", "version_date": "2026-02-24", "canonical_path": "/.well-known/ardp/meta", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/ardp/meta", "expect": { "json_keys": [ "ttl_min", "auth_profiles" ] }, "note": "ARDP meta declares TTL bounds and auth profiles." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-pioli-agent-discovery-01", "last_verified": "2026-10-23", "freshness": "current" }, "ads": { "id": "ads", "name": "Agent Directory Service", "acronym": "ADS", "step": "discover", "phase": "draft", "native_status": "Internet-Draft; work in progress; canonical spec tracked at spec.dir.agntcy.org", "current_version": "draft-mp-agntcy-ads-02", "version_date": "2026-07-06", "canonical_path": "/.well-known/ai-catalog.json (host-local AI Finder); GET /v1/agents (REST API)", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/v1/agents", "expect": { "content_type": "json", "text_match": "\"(agents|entries|items|records)\"\\s*:\\s*\\[" }, "note": "An Agent Directory Service lists catalog entries as a JSON array at /v1/agents." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-mp-agntcy-ads-02", "last_verified": "2026-10-29", "freshness": "current" }, "oasf": { "id": "oasf", "name": "Open Agentic Schema Framework", "acronym": "OASF", "step": "discover", "phase": "living", "native_status": "Active, versioned schema framework", "current_version": "v1.1.0", "version_date": "2026-07-10", "canonical_path": "none", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "OASF schemas live on the schema host, not on the origin using them." }, "spec_url": "https://schema.oasf.outshift.com/", "last_verified": "2026-10-23", "freshness": "current" }, "a2ui": { "id": "a2ui", "name": "A2UI (Agent to UI) Protocol", "acronym": "A2UI", "step": "present", "phase": "candidate", "native_status": "The README says \"Early stage public preview\" and \"A2UI's current production release is v0.9.1, a patch release in the stable v0.9 protocol family. The v1.0 specification is a release candidate, while v0.8 is legacy.\" [6]", "current_version": "v0.9.1", "version_date": "2025-12-03", "canonical_path": "No well-known path. Over A2A, an agent can list the A2UI extension in its Agent Card with the URI https://a2ui.org/a2a-extension/a2ui/v0.9.1 [17]; that URI is an identifier and returned HTTP 404 as a web page on 2026-10-28. The spec says \"Agents advertising A2UI support in their AgentCard is encouraged as clients may rely on it to determine if they should send message.metadata[\"a2uiClientCapabilities\"], however it is not explicitly required.\" [17]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "A2UI is carried inside an AG-UI, A2A or MCP session; no fixed path." }, "spec_url": "https://a2ui.org/specification/v0.9.1-a2ui/", "last_verified": "2026-10-28", "freshness": "current" }, "ag-ui": { "id": "ag-ui", "name": "Agent-User Interaction Protocol (AG-UI)", "acronym": "AG-UI", "step": "present", "phase": "stable", "native_status": "Stable. On 2026-09-18 the maintainers wrote: \"Following the draft period and the feedback collected here, AG-UI 1.0 is now officially released and frozen.\" \"The 1.0 specification will remain unchanged, while future protocol evolution will happen through new draft specifications and open community discussion before each release.\" [13][14]. The documentation says \"AG-UI 1.0 is the first release with a specification behind it\" [12], and CopilotKit says \"AG-UI 1.0 is backwards compatible, so your existing agents and apps keep working.\" [18]", "current_version": "Specification 1.0 (@ag-ui/core 1.0.3; release/2026-10-21)", "version_date": "2026-10-21", "canonical_path": "No well-known path or discovery document was found in the specification. A client is given the address of an agent endpoint and sends the run input to it as an HTTP POST [11]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "The AG-UI run endpoint is application-defined." }, "spec_url": "https://docs.ag-ui.com/spec/1.0/index", "last_verified": "2026-10-28", "freshness": "current" }, "osi": { "id": "osi", "name": "Apache Ossie (formerly Open Semantic Interchange)", "acronym": "Ossie", "step": "read", "phase": "draft", "native_status": "Draft specification; no Apache release yet. \"DRAFT version — in development, schema may change before 0.2.0 is released.\" [1]. \"Date of last release: None yet — no Apache release has been made since entering incubation.\" [17]. GitHub: \"There aren't any releases here\" [7]. Licence `\"spdx_id\": \"Apache-2.0\"` [4]", "current_version": "0.2.0.dev0 in development (last released spec version 0.1.1)", "version_date": "2025-12-11", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "OSI is a schema for semantic models exchanged between tools, not an origin artefact." }, "spec_url": "https://raw.githubusercontent.com/apache/ossie/main/core-spec/spec.md", "last_verified": "2026-10-29", "freshness": "current" }, "okf": { "id": "okf", "name": "Open Knowledge Format", "acronym": "OKF", "step": "read", "phase": "draft", "native_status": "Pre-1.0. Google called v0.1 \"a starting point, not a finished standard\" [5]. Repository licensed Apache-2.0 [2]", "current_version": "0.2", "version_date": "2026-07-24", "canonical_path": "/okf/index.md", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/okf/index.md", "expect": { "text_match": "(?m)^okf_version:\\s*\"?0\\.[12]\"?" }, "note": "Google Open Knowledge Format (OKF v0.2) web bundle index at /okf/index.md declaring okf_version." }, "spec_url": "https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md", "last_verified": "2026-10-28", "freshness": "current" }, "openai-apps-sdk-manifests": { "id": "openai-apps-sdk-manifests", "name": "OpenAI Apps SDK manifests", "acronym": null, "step": "act", "phase": "living", "native_status": "Preview at launch: \"Developers can access the SDK for making apps in preview starting today. Later this year, developers will be able to submit apps for review and publication, and OpenAI also plans to offer a directory for users to browse apps, according to OpenAI CEO Sam Altman.\" [14]. Submissions opened in December 2025: \"App developers looking to launch their programs in ChatGPT can now submit them for review and potential publication, OpenAI said Wednesday.\" \"OpenAI's Apps SDK, which is still in beta, currently provides a toolkit for developers looking to create new experiences for ChatGPT users.\" [15]. Changelog: \"2026-02-22 MCP Apps compatibility Fixes & improvements ChatGPT is now fully compatible with the MCP Apps spec.\" \"2026-03-25 Plugin distribution guidance Fixes & improvements Approved Apps SDK integrations could be distributed as Codex plugins. At launch, plugins were available only in Codex.\" [11]. Plugin extensions were launched on 2026-09-29: \"Altman said OpenAI is launching plugin extensions, which means developers can build plugins that are \"essentially entire applications that feel native to ChatGPT\" and are distributed through OpenAI.\" [17]. No general-availability statement for the Apps SDK was found in the live sources", "current_version": "1.0.0 (Agent Plugins schema)", "version_date": null, "canonical_path": "No public discovery file. Apps are found in the directory: \"ChatGPT and Codex share one universal plugin directory. When you publish a public plugin, people can discover the same listing from supported surfaces in either product.\" [5]. The only well-known path is for verifying domain ownership during submission, not for discovery: \"For domain verification, host the exact challenge token as plain text at the URL shown in the portal: https:///.well-known/openai-apps-challenge\" [7]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Plugin manifests are registered with OpenAI, reached through the app's MCP endpoint." }, "spec_url": "https://developers.openai.com/plugins/build/chatgpt-ui", "last_verified": "2026-10-29", "freshness": "current" }, "aamp": { "id": "aamp", "name": "Agentic Advertising Management Protocols", "acronym": "AAMP", "step": "coordinate", "phase": "living", "native_status": "Active umbrella initiative, current release AAMP 2.3, described by its own authors as 'far more than a single framework'", "current_version": "AAMP 2.3", "version_date": "2026-07-30", "canonical_path": "https://registry.iabtechlab.ai/", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "AAMP registries are operated by IAB Tech Lab, not by the origin." }, "spec_url": "https://github.com/IABTechLab/AAMP", "last_verified": "2026-10-23", "freshness": "current" }, "artf": { "id": "artf", "name": "Agentic Real Time Framework", "acronym": "ARTF", "step": "act", "phase": "stable", "native_status": "Final v1.0 specification, published after public comment; v2.0 development already underway", "current_version": "v1.0", "version_date": "2026-07-20", "canonical_path": "http://{host}:{health-port}/health/ready", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "ARTF containers run inside the host platform; the health endpoint is internal." }, "spec_url": "https://github.com/IABTechLab/agentic-real-time-framework", "last_verified": "2026-10-29", "freshness": "current" }, "adcp": { "id": "adcp", "name": "Ad Context Protocol (AdCP)", "acronym": "AdCP", "step": "act", "phase": "working-group", "native_status": "Active, generally available. Latest release `\"tag_name\": \"v3.2.8\"`, `\"published_at\": \"2026-10-28T20:56:12Z\"` [13]. \"**Status:** General availability, published 2026-09-30.\" [3]. Repository `\"archived\": false` [12]", "current_version": "v3.2.8", "version_date": "2026-10-28", "canonical_path": "/.well-known/adagents.json (publisher) and /.well-known/brand.json (brand/operator)", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/adagents.json", "expect": { "json_keys": [ "agents" ] }, "note": "adagents.json lists the publisher's authorised ad agents." }, "spec_url": "https://docs.adcontextprotocol.org/dist/docs/3.2.8/intro", "last_verified": "2026-10-29", "freshness": "current" }, "tap": { "id": "tap", "name": "Trusted Agent Protocol (TAP)", "acronym": "TAP", "step": "identify", "phase": "candidate", "native_status": "Published specification plus a sample implementation: \"Trusted Agent Protocol is available today in the Visa Developer Center and GitHub.\" [12]. The repository holds a sample agent, merchant, CDN proxy and Agent Registry [9][11]", "current_version": "None numbered", "version_date": null, "canonical_path": "In request headers sent by the agent, not on the merchant's site, so a merchant's use cannot be seen from outside. Merchant side: \"The core of the protocol is simple: a trusted agent will include a message signature in its request to your server. A merchant's primary task is to validate this signature.\" [2]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "Trusted Agent Protocol keys are fetched from the key service by keyID during a transaction." }, "spec_url": "https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications", "last_verified": "2026-10-29", "freshness": "current" }, "vi": { "id": "vi", "name": "Verifiable Intent", "acronym": "VI", "step": "account", "phase": "draft", "native_status": "Draft (v0.1); open-sourced specification and reference implementation", "current_version": "0.1-draft", "version_date": "2026-02-18", "canonical_path": "/.well-known/verifiable-intent", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/verifiable-intent", "expect": { "content_type": "json", "text_match": "\"(verifiable_intent|intent|vct|keys|sd-jwt|kb-sd-jwt)\"\\s*:" }, "note": "A merchant publishes its Verifiable Intent document at a fixed well-known path." }, "spec_url": "https://verifiableintent.dev/spec/", "last_verified": "2026-10-23", "freshness": "current" }, "spiffe": { "id": "spiffe", "name": "SPIFFE (Secure Production Identity Framework for Everyone)", "acronym": "SPIFFE", "step": "identify", "phase": "stable", "native_status": "SPIFFE ID, X.509-SVID, JWT-SVID, Workload API, Workload Endpoint, Trust Domain and Bundle and Federation are each marked \"Stability: Stable\" [11][12][13][14][15][16][17]. WIT-SVID is marked \"Stability: Incubating\" [19], as is the WIT-SVID section of the Workload API: \"Stability: Incubating (this section only - the remainder of this document is Stable.)\" [14]", "current_version": "SPIRE v1.15.5 (specifications carry stability levels rather than version numbers)", "version_date": "2026-10-20", "canonical_path": "No public web URL. A workload reads its identity from the local SPIFFE Workload Endpoint, which the specification describes this way: \"The SPIFFE Workload Endpoint MUST be served over gRPC, and compliant clients MUST support gRPC. It may be exposed as either a Unix Domain Socket (UDS) or a TCP listen socket.\" [15]. Between trust domains, bundles are published at a bundle endpoint URL that each operator chooses [17]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "SPIFFE identities are issued over a local socket, not published on the web." }, "spec_url": "https://spiffe.io/docs/latest/spiffe-about/overview/", "last_verified": "2026-10-28", "freshness": "current" }, "wimse": { "id": "wimse", "name": "Workload Identity in Multi System Environments (WIMSE)", "acronym": "WIMSE", "step": "identify", "phase": "working-group", "native_status": "No WIMSE RFC has been published: the Datatracker lists no RFC for the group (checked 2026-10-28) [4]. Furthest along: draft-ietf-wimse-http-signature-08, \"WG state Submitted to IESG for Publication\" \"IESG state Publication Requested\"; the history records \"IESG state changed to Publication Requested from I-D Exists\" on 2026-10-28 [11][12]. draft-ietf-wimse-workload-identity-practices-07 was submitted to the IESG on 2026-06-30 and is in \"IESG state AD Evaluation::AD Followup\" [18][19]. All other current documents are active working-group drafts in \"WG Document\" state with IESG state \"I-D Exists\" [3][5]", "current_version": "Working-group drafts, latest revision and date as the Datatracker shows them: draft-ietf-wimse-arch-08 (2026-07-06); draft-ietf-wimse-workload-creds-02 (2026-07-02); draft-ietf-wimse-wpt-02 (2026-08-27); draft-ietf-wimse-http-signature-08 (latest revision 2026-10-20, \"Last updated 2026-10-28 (Latest revision 2026-10-20)\"); draft-ietf-wimse-mutual-tls-03 (2026-10-24); draft-ietf-wimse-identifier-04 (2026-10-23); draft-ietf-wimse-workload-identity-practices-07 (2026-09-22); draft-ietf-wimse-aims-00 (2026-09-15) [3][5][7][9][11][14][16][18][22]", "version_date": "2026-07-06", "canonical_path": "HTTP request headers between workloads. The WIT travels in its own header field: \"ABNF [RFC5234] for the value of Workload-Identity-Token header field\" [8]. A WPT goes in the Authorization header: \"The WPT is sent in the Authorization header field (Section 11.6.2 of [RFC9110]) of the request, using the WPT authentication scheme defined by this document.\" [10]. The HTTP-signature profile signs requests with RFC 9421 and sets \"tag - the value for implementations of this specification is wimse-workload-to-workload\" [13]. The mutual-TLS profile uses X.509 certificates in the TLS handshake [15]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "WIMSE is an architecture for workload identity with no origin artefact." }, "spec_url": "https://datatracker.ietf.org/wg/wimse/documents/", "last_verified": "2026-10-28", "freshness": "current" }, "aauth": { "id": "aauth", "name": "Agent Authorization Grant", "acronym": "AAuth", "step": "permit", "phase": "deprecated", "native_status": "Expired Internet-Draft (expired 2026-04-23)", "current_version": "draft-rosenberg-oauth-aauth-01", "version_date": "2026-04-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "The Agent Authorization Grant is observed only inside a token request." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-rosenberg-oauth-aauth", "last_verified": "2026-10-23", "freshness": "current" }, "daap": { "id": "daap", "name": "OAuth Profile for Delegated AI Agent Authorization", "acronym": "DAAP", "step": "permit", "phase": "draft", "native_status": "Internet-Draft, individual submission, Active", "current_version": "draft-mishra-oauth-agent-grants-02", "version_date": "2026-08-30", "canonical_path": "/.well-known/oauth-authorization-server", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "DAAP rides on OAuth authorization server metadata; presence of that metadata does not prove the profile." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-mishra-oauth-agent-grants-02", "last_verified": "2026-10-29", "freshness": "current" }, "aap": { "id": "aap", "name": "Agent Authorization Profile", "acronym": "AAP", "step": "permit", "phase": "deprecated", "native_status": "Expired Internet-Draft (expired 2026-08-11)", "current_version": "draft-aap-oauth-profile-01", "version_date": "2026-02-07", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "AAP is a claims profile inside OAuth tokens; nothing at a fixed path proves it." }, "spec_url": "https://www.ietf.org/archive/id/draft-aap-oauth-profile-01.html", "last_verified": "2026-10-23", "freshness": "current" }, "aip": { "id": "aip", "name": "Agent Identity Protocol (AIP)", "acronym": "AIP", "step": "identify", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track (author's stated intent; not adopted by any WG)", "current_version": "draft-singla-agent-identity-protocol-03, published 2026-06-10", "version_date": "2026-06-10", "canonical_path": "none", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "client-side", "note": "AIP is a client-side identity protocol with no origin artefact." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-singla-agent-identity-protocol-03", "last_verified": "2026-10-29", "freshness": "current" }, "agtp": { "id": "agtp", "name": "Agent Transfer Protocol", "acronym": "AGTP", "step": "coordinate", "phase": "draft", "native_status": "Internet-Draft (work in progress), independent submission", "current_version": "draft-hood-independent-agtp-09", "version_date": "2026-06-28", "canonical_path": "none", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "AGTP is its own application-layer protocol over QUIC or TCP." }, "spec_url": "https://www.ietf.org/archive/id/draft-hood-independent-agtp-09.html", "last_verified": "2026-10-29", "freshness": "current" }, "vcap": { "id": "vcap", "name": "VCAP: Verified Commerce for Agent Protocols", "acronym": "VCAP", "step": "pay", "phase": "draft", "native_status": "Active Internet-Draft (individual); Intended status: Informational (draft header; Datatracker stream status is None)", "current_version": "draft-stone-vcap-02", "version_date": "2026-09-04", "canonical_path": "none", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "VCAP credentials are presented during a payment, not published." }, "spec_url": "https://www.ietf.org/archive/id/draft-stone-vcap-02.html", "last_verified": "2026-10-29", "freshness": "current" }, "anp": { "id": "anp", "name": "Agent Network Protocol", "acronym": "ANP", "step": "coordinate", "phase": "stable", "native_status": "Released v1.2 (core suite); meta-protocol (ANP-06) remains draft/unreleased", "current_version": "v1.2", "version_date": "2026-09-24", "canonical_path": "/.well-known/agent-descriptions", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent-descriptions", "expect": { "content_type": "json", "text_match": "AgentDescription" }, "note": "ANP active discovery is a JSON-LD collection of AgentDescription items." }, "spec_url": "https://github.com/agent-network-protocol/AgentNetworkProtocol", "last_verified": "2026-10-29", "freshness": "current" }, "agora-protocol": { "id": "agora-protocol", "name": "Agora Protocol", "acronym": null, "step": "coordinate", "phase": "draft", "native_status": "Draft, and inactive since March 2025. \"Below is the Working Standard for the Agora Protocol, structured in a style similar to IETF RFCs. It includes the sections outlined previously, along with normative language (per RFC 2119 and RFC 8174). While this document follows a typical RFC format, it should be understood as a draft.\" [3] \"We're building the next iteration of Agora, with more features for real-world use cases.\" [7] \"This document is intended to be a Proposed Standard.\" [3] The library says \"Agora Python is currently in Open Beta! Expect breaking changes from one version to the other.\" [8] The last commit in the organisation is dated 2025-03-08 (UTC), in agora-protocol/python [9], 600 days before this check.", "current_version": "Working Standard (2025-01-19); agora-protocol 0.2.0", "version_date": "2025-01-19", "canonical_path": "{baseURL}/wellknown", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.wellknown", "expect": { "content_type": "json", "text_match": "^\\s*\\{\\s*\"[A-Za-z0-9_-]{8,}\"\\s*:\\s*\\[\\s*\"https?://" }, "note": "Agora agents declare supported protocols at /.wellknown (sic) as a JSON map from protocol hash strings to arrays of protocol-document URLs." }, "spec_url": "https://agoraprotocol.org/docs/protocol/specification", "last_verified": "2026-10-29", "freshness": "current" }, "agora-commerce-protocol": { "id": "agora-commerce-protocol", "name": "Agora (agent marketplace protocol)", "acronym": null, "step": "pay", "phase": "candidate", "native_status": "Testnet-only; production_status explicitly \"testnet-only\" in its own manifest", "current_version": "API 0.1.0, contract V2 live on Base Sepolia since 2026-05-29 (V1 legacy; V2.1 not deployed)", "version_date": "2026-05-29", "canonical_path": "https://api.agoraproto.org/.well-known/ai-services.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Agora Commerce publishes at api.agoraproto.org, not on member origins." }, "spec_url": "https://api.agoraproto.org/v1/openapi.json", "last_verified": "2026-10-29", "freshness": "current" }, "s402": { "id": "s402", "name": "s402", "acronym": "s402", "step": "pay", "phase": "deprecated", "native_status": "Archived repository (observed 2026-10-16)", "current_version": "Wire Format Specification v1, Draft, dated March 2026 (repository has continued past this to align with x402 v2)", "version_date": "2026-03", "canonical_path": "none — no /.well-known/s402.json was found; discovery is per-request via the 402 envelope, matching x402's model", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "s402 challenges appear only on paid URLs." }, "spec_url": "https://raw.githubusercontent.com/s402-protocol/core/main/docs/specification.md", "last_verified": "2026-10-23", "freshness": "current" }, "agent-attribution-protocol": { "id": "agent-attribution-protocol", "name": "Agent Attribution Protocol", "acronym": "AAP", "step": "account", "phase": "stable", "native_status": "\"The open standard for AI agent affiliate attribution\" (vendor's own description); v1.0 spec published, centrally operated", "current_version": "v1.0", "version_date": "2026-04-02", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "The probe is a vendor API call that needs an API key." }, "spec_url": "https://github.com/rakohq/aap-spec", "last_verified": "2026-10-29", "freshness": "current" }, "agent-audit-trail": { "id": "agent-audit-trail", "name": "Agent Audit Trail", "acronym": "AAT", "step": "account", "phase": "draft", "native_status": "Active Internet-Draft (individual submission), Intended status: Standards Track; not a Working Group document", "current_version": "draft-sharif-agent-audit-trail-09", "version_date": "2026-10-26", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "Audit logs are exported from an operator-defined endpoint behind authentication." }, "spec_url": "https://www.ietf.org/archive/id/draft-sharif-agent-audit-trail-09.txt", "last_verified": "2026-10-29", "freshness": "current" }, "slim": { "id": "slim", "name": "Secure Low-Latency Interactive Messaging (SLIM)", "acronym": "SLIM", "step": "coordinate", "phase": "draft", "native_status": "Released open-source software at major version 3 (slim-v3.4.6 / slimctl-v3.4.6, 2026-10-20); individual IETF Internet-Draft draft-mpsb-agntcy-slim-02 in state \"I-D Exists\" (Informational, expires 2027-01-20) [9][10][11][13]", "current_version": "slim-v3.4.6 / slimctl-v3.4.6 (2026-10-20); draft-mpsb-agntcy-slim-02 (2026-07-19)", "version_date": "2026-07-19", "canonical_path": "none — hierarchical name routing (`organization/namespace/service/instance`) [13]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "SLIM is a transport operated by data-plane nodes on its own wire protocol." }, "spec_url": "https://www.ietf.org/archive/id/draft-mpsb-agntcy-slim-02.html", "last_verified": "2026-10-29", "freshness": "current" }, "api-catalog-rfc9727": { "id": "api-catalog-rfc9727", "name": "api-catalog (RFC 9727)", "acronym": "RFC 9727", "step": "discover", "phase": "stable", "native_status": "Proposed Standard [2]. One technical erratum (ID 9009, about the Section 5.1 nesting example) reported 2026-06-21, status \"Reported\" (not verified) [6]", "current_version": "RFC 9727", "version_date": "2025-06-13", "canonical_path": "/.well-known/api-catalog", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/api-catalog", "expect": { "content_type": "linkset", "json_keys": [ "linkset" ] }, "note": "RFC 9727 requires application/linkset+json with a linkset array at /.well-known/api-catalog (probe and validate_manifest also observe Link: rel=api-catalog headers on /)." }, "spec_url": "https://www.rfc-editor.org/rfc/rfc9727.html", "last_verified": "2026-10-28", "freshness": "current" }, "rsl": { "id": "rsl", "name": "Really Simple Licensing", "acronym": "RSL", "step": "permit", "phase": "stable", "native_status": "Recommendation (RSL's own maturity label, not a W3C/IETF Recommendation) — Document RSL-SPEC-1.0, Category 'Industry Specification'", "current_version": "RSL 1.0", "version_date": "2025-12-10", "canonical_path": "/rsl.xml", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/robots.txt", "expect": { "text_match": "(?im)^license:\\s*\\S|rsl\\.xml" }, "note": "RSL is referenced from robots.txt by a License line or an rsl.xml link." }, "spec_url": "https://rslstandard.org/rsl", "last_verified": "2026-10-23", "freshness": "current" }, "agent-permissions-json": { "id": "agent-permissions-json", "name": "agent-permissions.json", "acronym": null, "step": "permit", "phase": "candidate", "native_status": "Work-in-progress draft (\"Note: This standard is still WIP!\"); metadata.schema_version uses semantic versioning (^\\d+\\.\\d+\\.\\d+$, illustrated as \"1.0.0\" in examples), with zero tagged GitHub releases [2][3][4]", "current_version": "v0.3 draft (schema_version 1.0.0)", "version_date": "2025-12-10", "canonical_path": "/.well-known/agent-permissions.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agent-permissions.json", "expect": { "json_keys": [ "metadata", "strict" ] }, "note": "agent-permissions.json requires metadata and strict at top level." }, "spec_url": "https://github.com/las-wg/agent-permissions.json", "last_verified": "2026-10-29", "freshness": "current" }, "auth-md": { "id": "auth-md", "name": "auth.md", "acronym": null, "step": "permit", "phase": "draft", "native_status": "Reference specification at `v0.6.0` (10 June 2026); generally available in WorkOS AuthKit (`Agent Registration`) since 4 August 2026 [4][5][13][18]", "current_version": "v0.6.0", "version_date": "2026-06-10", "canonical_path": "/auth.md", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/auth.md", "expect": { "text_match": "identity_assertion|service_auth|anonymous" }, "note": "auth.md describes one or more of the three named flows." }, "spec_url": "https://github.com/workos/auth.md", "last_verified": "2026-10-29", "freshness": "current" }, "oauth-metadata-for-agents": { "id": "oauth-metadata-for-agents", "name": "OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)", "acronym": null, "step": "permit", "phase": "stable", "native_status": "Proposed Standard (RFC 8414, published June 2018) and Proposed Standard (RFC 9728, published April 2025); both are products of IETF consensus, not works in progress", "current_version": "RFC 8414 (2018-06) and RFC 9728 (2025-04)", "version_date": "2025-04", "canonical_path": "/.well-known/oauth-protected-resource", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/oauth-protected-resource", "expect": { "json_keys": [ "resource" ] }, "note": "RFC 9728 protected resource metadata requires the resource field." }, "spec_url": "https://www.rfc-editor.org/rfc/rfc9728.html", "last_verified": "2026-10-24", "freshness": "current" }, "ai-crawler-tokens-robots": { "id": "ai-crawler-tokens-robots", "name": "AI crawler tokens in robots.txt", "acronym": null, "step": "permit", "phase": "living", "native_status": "In production: 11 vendors' tokens documented on pages fetched today, and named by 32 of the 36 sites probed", "current_version": "RFC 9309", "version_date": "2022-09", "canonical_path": "/robots.txt", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/robots.txt", "expect": { "text_match": "(?im)^user-agent:\\s*(GPTBot|OAI-SearchBot|ClaudeBot|Claude-User|Claude-SearchBot|Google-Extended|PerplexityBot|CCBot|Applebot-Extended|meta-externalagent|Bytespider|Amazonbot)\\b" }, "note": "A robots.txt group naming a known AI crawler token. In probe/has, any group naming a known AI crawler token counts as found; in validate_manifest, permit step coverage requires at least one allowed/partial AI crawler, Content-Signal, Content-Usage, or Agentmap directive." }, "spec_url": "https://www.rfc-editor.org/rfc/rfc9309.html", "last_verified": "2026-10-29", "freshness": "current" }, "mcp-apps": { "id": "mcp-apps", "name": "MCP Apps", "acronym": "MCP Apps", "step": "present", "phase": "candidate", "native_status": "SEP-1865 Final [1]. History: proposed and pull request #1865 opened on 2025-11-21 [9][2]; the stable 2026-01-26 specification and SDK v1.0.0 were released on 2026-01-26 [7], the day MCP Apps went live as \"the first official MCP extension\" [10]; #1865 merged on 2026-01-28 [2]. The repository lists 2026-01-26 as Stable and a draft as Development [4]. When checked, the SEP's Sponsor field still read \"None (seeking sponsor)\" [1]", "current_version": "2026-01-26", "version_date": "2026-01-26", "canonical_path": "No well-known path. A UI is a ui:// resource on the MCP server, for example ui://excalidraw/mcp-app.html, and the host reads it with resources/read [3]. Hosts find these resources mainly through _meta.ui.resourceUri in tools/list, and servers may leave UI-only resources out of resources/list [3]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "MCP Apps are declared inside an MCP server's tools/list; find the server first." }, "spec_url": "https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx", "last_verified": "2026-10-28", "freshness": "current" }, "vercel-agent-readability": { "id": "vercel-agent-readability", "name": "Agent Readability Spec", "acronym": "ARS", "step": "read", "phase": "draft", "native_status": "Original KB URL (`https://vercel.com/kb/guide/agent-readability-spec` and `.md`) returns `HTTP 301 / 308 Permanent Redirect` to *Make your site readable by AI agents | Vercel Knowledge Base* (`v1.0`, published 28 August 2026, last updated 3 September 2026) [1][2]; open standard `AgentReady v2.0` published October 2026 (`spec/spec.md` in `agentready-org/standard`) [12][13]; `a14y` scorecard `v0.2.0` released 6 April 2026 (`38` pinned checks) [7][8]", "current_version": "Vercel KB guide v1.0 (2026-08-28, updated 2026-09-03); AgentReady v2.0 (2026-10); @vercel/agent-readability v0.7.0 (2026-09-04); a14y v0.2.0 (2026-04-06)", "version_date": "2026-10", "canonical_path": "{origin}/llms.txt, /robots.txt, /sitemap.xml, /sitemap.md, /AGENTS.md, Accept: text/markdown", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "A checklist, not a manifest; the llms-txt, agents-md, robots and sitemap checks cover its site-level items." }, "spec_url": "https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents", "last_verified": "2026-10-29", "freshness": "current" }, "agents-json": { "id": "agents-json", "name": "agents.json", "acronym": null, "step": "act", "phase": "deprecated", "native_status": "Dormant in public repository development (\"archived\": false, last commit 5f5e60a4074eb0fb2aed5a3b03c8149dc3fd7120 on 2025-08-21: \"\"date\": \"2025-08-21T22:17:45Z\" }, \"message\": \"Update README.md\"\") [11][12]; Wildcard's primary domain (wild-card.ai) now markets AI search optimization for e-commerce storefronts (\"Ecommerce and retail brands use Wildcard to win every AI shopping surface. Track what ranks, act on the roadmap, and measure revenue.\") [30][31]", "current_version": "0.1.0", "version_date": "2025-03", "canonical_path": "Proposed at /.well-known/agents.json (\"We propose the file placed in /.well-known/agents.json so it is easily discoverable by agents accessing web services. For now, we maintain a registry for available agents.json files.\") [1][3], or loaded directly as standalone JSON files alongside OpenAPI specs from a repository or registry (\"We can begin building agents.json files immediately before official adoption by providers. No extra infrastructure changes, servers, or new endpoints. By putting responsibility of execution on the client - the paradigm abides by the same security and orchestration protocol of existing API based applications today. API providers can still choose to maintain official agents.json files.\") [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/agents.json", "expect": { "json_keys": [ "flows" ] }, "note": "agents.json extends OpenAPI with a flows field." }, "spec_url": "https://github.com/wild-card-ai/agents-json/blob/master/agents_json/agentsJson.schema.json", "last_verified": "2026-10-29", "freshness": "current" }, "agents-txt": { "id": "agents-txt", "name": "agents.txt", "acronym": null, "step": "discover", "phase": "idea", "native_status": "\"Status Draft This document is a work in progress and subject to change.\" [1]", "current_version": "1.0", "version_date": "2026-05-10", "canonical_path": "\"agents.txt MUST be served at /agents.txt. agents.json SHOULD be served at /agents.json.\" [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/agents.txt", "expect": { "text_match": "(?im)^(user-agent|agent|allow|disallow|endpoint|sitemap|policy|auth|rate-limit|crawl-delay)\\s*:|^#\\s*agents\\.txt\\b" }, "note": "agents.txt must contain robots-style or key-value directives (User-agent:, Agent:, Allow:, Disallow:, Endpoint:, Sitemap:, Policy:) or an # agents.txt header at /agents.txt, not a redirected documentation page." }, "spec_url": "https://agents-txt.com/spec/", "last_verified": "2026-10-29", "freshness": "current" }, "ai-txt": { "id": "ai-txt", "name": "ai.txt", "acronym": null, "step": "permit", "phase": "draft", "native_status": "Spawning `/ai.txt`: shipping generator and WordPress plugin v1.0 (30 May 2023) [1][2][3]; Cardillo `/.well-known/ai.txt`: individual IETF Internet-Draft `draft-car-ai-txt-wellknown-00` (12 June 2026, expires 14 December 2026) with IANA filings `#76`/`#77` rejected and closed on 16 March 2026 [5][6][8][9]", "current_version": "1.0 / draft-car-ai-txt-wellknown-00", "version_date": "2026-06-12", "canonical_path": "/ai.txt or /.well-known/ai.txt", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/ai.txt", "expect": { "text_match": "(?im)^(training|scraping|indexing|caching)\\s*:" }, "note": "ai.txt carries Training, Scraping, Indexing or Caching directives." }, "spec_url": "https://github.com/kaylacar/ai-txt/blob/master/ietf/draft-car-ai-txt-wellknown-00.md", "last_verified": "2026-10-30", "freshness": "current" }, "lmos": { "id": "lmos", "name": "Eclipse LMOS (Language Model Operating System)", "acronym": "LMOS", "step": "discover", "phase": "draft", "native_status": "Protocol: \"Please note that this protocol is work in progress and contains empty sections.\" [1]. Platform: \"Eclipse LMOS Platform: An open, vendor-neutral orchestration layer for agent lifecycle management, discovery, semantic routing, and observability, built on the CNCF stack and currently in Alpha.\" [13]. heise, in German: \"Die LMOS-Plattform befindet sich noch im Alphastadium und soll als offene Orchestrierungsschicht für die Infrastruktur dienen und basiert auf den Open-Source-Tools aus dem Ökosystem der CNCF (Cloud Native Computing Foundation).\" [31]. Project: \"State Incubating\" [7]", "current_version": "Namespace v1 (Arc 0.234.0; LMOS Runtime 0.32.0)", "version_date": "2026-09-02", "canonical_path": "/.well-known/wot", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/wot-thing-description", "expect": { "text_match": "eclipse\\.dev/lmos" }, "note": "An LMOS Thing Description references the LMOS namespace." }, "spec_url": "https://eclipse.dev/lmos/docs/lmos_protocol/introduction/", "last_verified": "2026-10-29", "freshness": "current" }, "agent-connect-protocol": { "id": "agent-connect-protocol", "name": "Agent Connect Protocol", "acronym": "ACP", "step": "act", "phase": "deprecated", "native_status": "Deprecated by AGNTCY in favour of A2A (since OASF v0.8.0, 2025-10-22), and archived read-only on 2026-04-11 [8][9]", "current_version": "0.2.3 (OpenAPI 3.1.1; 0 releases, 0 tags, last commit 2025-05-23; Python SDK agntcy-acp v1.5.2 of 2025-06-16)", "version_date": "2025-05-23", "canonical_path": "/agents/search", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /agents/search." }, "spec_url": "https://github.com/agntcy/acp-spec", "last_verified": "2026-10-29", "freshness": "current" }, "agent-protocol-aief": { "id": "agent-protocol-aief", "name": "Agent Protocol", "acronym": "AP", "step": "act", "phase": "deprecated", "native_status": "Dormant: no push since 2025-04-08 (repository not archived). \"Common interface for interacting with AI agents. The protocol is tech stack agnostic\" (repository description); defined as an OpenAPI REST spec with two core routes, POST /ap/v1/agent/tasks and POST /ap/v1/agent/tasks/{task_id}/steps", "current_version": "unversioned OpenAPI spec (schemas/openapi.yml)", "version_date": null, "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /ap/v1/agent/tasks, which starts a task." }, "spec_url": "https://github.com/agi-inc/agent-protocol", "last_verified": "2026-10-29", "freshness": "current" }, "aitp": { "id": "aitp", "name": "Agent Interaction & Transaction Protocol (AITP)", "acronym": "AITP", "step": "coordinate", "phase": "draft", "native_status": "Draft, and inactive. \"Version: 0.1.0 Status: Draft\" [1]. Latest commit `\"date\": \"2025-04-01T15:09:48Z\"` [10]. An open issue, `\"title\": \"Activity question\"`, `\"created_at\": \"2026-06-12T05:21:10Z\"`, has `\"comments\": 0` replies [15]. The repository is not archived (`\"archived\": false`) [9], but the NEAR AI Hub that ran it is closed: \"The NEAR AI Developer Hub at https://app.near.ai/ will shut down on October 31, 2025 and replaced with this notice.\" [19]", "current_version": "0.1.0 (Draft)", "version_date": null, "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /threads, which creates a thread." }, "spec_url": "https://aitp.dev/", "last_verified": "2026-10-29", "freshness": "current" }, "coral-protocol": { "id": "coral-protocol", "name": "Coral Protocol (CoralOS)", "acronym": "Coral", "step": "coordinate", "phase": "living", "native_status": "\"Kubernetes for AI agents: a platform for everything between your agents and production — registry, runtimes, security, and orchestration\" (current docs homepage); described elsewhere as a 'decentralized protocol powering AI agent collaboration, trust, and payments'", "current_version": "unversioned, continuously updated platform (Coral Server, Coralizer, Marketplace)", "version_date": null, "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "unsafe-post", "note": "The probe is POST /api/v1/local/session, which opens a session." }, "spec_url": "https://docs.coralos.ai/welcome", "last_verified": "2026-10-29", "freshness": "current" }, "web-agent-protocol": { "id": "web-agent-protocol", "name": "Web Agent Protocol (WAP)", "acronym": "WAP", "step": "act", "phase": "deprecated", "native_status": "Dormant: last commit 2025-06-03", "current_version": "unversioned (main branch, 1 tag, last commit 2025-06-03)", "version_date": "2025-06-03", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "client-side", "note": "WAP records and replays browser actions; nothing is served by the site." }, "spec_url": "https://github.com/OTA-Tech-AI/web-agent-protocol", "last_verified": "2026-10-23", "freshness": "current" }, "nlip": { "id": "nlip", "name": "Natural Language Interaction Protocol (NLIP)", "acronym": "NLIP", "step": "coordinate", "phase": "stable", "native_status": "Approved and published by Ecma in December 2025. \"The 130th General Assembly held in Geneva on 10 December 2025 approved the following documents:\" `ECMA-430 1st edition – Natural Language Interaction Protocol (NLIP)` … `ECMA TR/113 1st edition – Explanatory guide to the Natural Language Interaction Protocol (NLIP)` [11]. The PDF: \"This Ecma Standard was developed by Technical Committee 56 and was adopted by the General Assembly of December 2025.\" [2]. \"Ecma International published on 10 December 2025 five new standards and one technical report defining the Natural Language Interaction Protocol (NLIP).\" [12]", "current_version": "ECMA-430, 1st edition (nlip_sdk 0.1.3)", "version_date": "2025-12-10", "canonical_path": "{origin}/nlip", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "NLIP is a message envelope between agents; ECMA-430 defines no discovery artefact at an origin." }, "spec_url": "https://ecma-international.org/publications-and-standards/standards/ecma-430/", "last_verified": "2026-10-29", "freshness": "current" }, "emv-agentic-payments": { "id": "emv-agentic-payments", "name": "EMV® Agentic Payments – Framework for Specifications", "acronym": "EMV Agentic Payments", "step": "pay", "phase": "draft", "native_status": "Draft. Public comments were due on 30 September 2026 [2]; PYMNTS reported on 2026-10-02: \"The standards body closed public comments Sept. 30 on its Agentic Payments — Framework for Specifications\" [19]. The 2026-10-09 newsletter still lists \"EMV® Agentic Payments – Framework for Specifications Version 1.0 (Draft) Framework to help promote secure, interoperable and scalable card-based agentic payments, which introduces the concept of 'Intent Services'.\" [6]. No later version appears on the EMVCo pages fetched on 2026-10-29", "current_version": "v1.0 DRAFT", "version_date": "2026-08-30", "canonical_path": "Nothing to probe. It is a framework document, with no endpoint, file or header of its own [2]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "A framework document for card-network payment specifications; nothing is published at an origin." }, "spec_url": "https://www.emvco.com/resources/emv-agentic-payments-framework-for-specifications-v1-0-draft-comment-period-ends-30-sept-2026/", "last_verified": "2026-10-29", "freshness": "current" }, "identity-assertion-authz-grant": { "id": "identity-assertion-authz-grant", "name": "Identity Assertion JWT Authorization Grant (ID-JAG)", "acronym": "ID-JAG", "step": "permit", "phase": "working-group", "native_status": "Active Internet-Draft. \"WG state WG Document\"; \"IESG state I-D Exists\" [1]. Not an RFC; the draft's IANA requests are not yet in the OAuth Parameters registry (scanned live) [6]", "current_version": "draft-ietf-oauth-identity-assertion-authz-grant-04 (replaces the individual draft-parecki-oauth-identity-assertion-authz-grant)", "version_date": "2026-05-21", "canonical_path": "/.well-known/oauth-authorization-server or /.well-known/openid-configuration", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/oauth-authorization-server", "expect": { "json_keys": [ "authorization_grant_profiles_supported" ] }, "note": "draft-ietf-oauth-identity-assertion-authz-grant advertises the id-jag profile in authorization server metadata; the key alone shows the server publishes grant profiles, so check for urn:ietf:params:oauth:grant-profile:id-jag in the value." }, "spec_url": "https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-assertion-authz-grant/", "last_verified": "2026-10-29", "freshness": "current" }, "aiagent-auth": { "id": "aiagent-auth", "name": "AI Agent Authentication and Authorization", "acronym": null, "step": "identify", "phase": "replaced", "native_status": "Replaced. Datatracker shows this draft as \"Replaced by draft-ietf-wimse-aims\" [1]. This is a history page: it is not updated by the IETF tracker, and the working-group draft's current revision and dates are on [AI Identity Management System (AIMS)](/protocols/wimse-aims/)", "current_version": "draft-klrc-aiagent-auth-03", "version_date": "2026-07-06", "canonical_path": "Nothing to discover: the draft defines no endpoint or registry entry. \"This document has no IANA actions.\" [5]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "An IETF framework draft composing WIMSE, SPIFFE and OAuth flows; it defines no artefact of its own at an origin." }, "spec_url": "https://datatracker.ietf.org/doc/draft-klrc-aiagent-auth/", "last_verified": "2026-10-30", "freshness": "current" }, "dan": { "id": "dan", "name": "DNS-Based Agent Naming", "acronym": "DAN", "step": "discover", "phase": "draft", "native_status": "Active Internet-Draft (individual, -00), Intended status: Standards Track; IESG state 'I-D Exists'; expires 7 December 2026", "current_version": "draft-seethiraju-dawn-dan-00, 5 June 2026 (single published version; no -01 as of 2026-09-07)", "version_date": "2026-06-05", "canonical_path": "_agents. (AIINDEX, TYPE65502); ._agents. (AIDISCA, TYPE65501)", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "DNS records of types AIINDEX (65502) at _agents. and AIDISCA (65501); not reachable by HTTP GET." }, "spec_url": "https://datatracker.ietf.org/doc/draft-seethiraju-dawn-dan/", "last_verified": "2026-10-29", "freshness": "current" }, "mcp-registry": { "id": "mcp-registry", "name": "Official MCP Registry", "acronym": "MCP Registry", "step": "discover", "phase": "candidate", "native_status": "Preview. The documentation says \"The MCP Registry is currently in preview. Breaking changes or data resets may occur before general availability.\" [1] (checked 2026-10-28). Launched in preview 2025-09-08 [3]; API v0.1 frozen from 2025-10-24 [4]. \"Registry API v1 GA\" is listed as Ideating, with no target date [2]. No documentation was found showing a general-availability date", "current_version": "API v0.1, the stable path, introduced 2025-10-17; /v0 remains the development path [5][4]. server.json schema 2025-12-11 [12][14]. The running service reports release 1.8.6, built 2026-10-27 [13]", "version_date": null, "canonical_path": "https://registry.modelcontextprotocol.io · GET /v0.1/servers (cursor pagination, updated_since filter), GET /v0.1/servers/{serverName}/versions, GET /v0.1/servers/{serverName}/versions/{version} (or latest) [9]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://modelcontextprotocol.io/registry/about", "last_verified": "2026-10-28", "freshness": "current" }, "wimse-aims": { "id": "wimse-aims", "name": "AI Identity Management System (AIMS)", "acronym": "AIMS", "step": "identify", "phase": "working-group", "native_status": "Adopted working-group draft, early stage. \"WG state WG Document\" \"IESG state I-D Exists\" \"Document shepherd (None)\" [1]. Adopted 2026-09-09: \"2026-09-09 03 Justin Richer IETF WG state changed to Adopted by a WG\" [6]; the predecessor is \"state\": \"Replaced\" [5]", "current_version": "draft-ietf-wimse-aims-00", "version_date": "2026-09-15", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/draft-ietf-wimse-aims/", "last_verified": "2026-10-29", "freshness": "current" }, "personal-agent-protocol": { "id": "personal-agent-protocol", "name": "Personal Agent Protocol", "acronym": "Poppy", "step": "identify", "phase": "draft", "native_status": "Draft. \"The specification is a draft.\" [6]. \"It's a draft, and we're working with design partners to get it to 1.0.\" [7]. Repository last push `\"pushed_at\": \"2026-10-26T18:13:13Z\"` [9]; the repository had no tags or releases when checked. Licence: \"Licensed under the Apache License 2.0.\" [7]", "current_version": "0.2 is the latest published version: \"Version 0.2 Published October 24, 2026. It's frozen at /docs/0.2/spec.\" [1] Draft 0.3 is in progress: \"Draft 0.3 In progress, at /docs/spec. This list grows until 0.3 is published.\" [1]; \"This draft is 0.3.\" [2]. First version: \"Version 0.1 Published October 9, 2026, the first published draft. It's frozen at /docs/0.1/spec.\" [1]", "version_date": "2026-10-24", "canonical_path": "/.well-known/poppy.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://personalagentprotocol.org/docs/0.2/spec", "last_verified": "2026-10-29", "freshness": "current" }, "aauth-hardt": { "id": "aauth-hardt", "name": "AAuth (Hardt)", "acronym": "AAuth", "step": "permit", "phase": "draft", "native_status": "Active Internet-Draft (individual), expires 2027-03-29 UTC: \"expires\": \"2027-03-29T16:59:56Z\" [2]", "current_version": "draft-hardt-oauth-aauth-protocol-11", "version_date": "2026-09-25", "canonical_path": "/.well-known/aauth-resource.json (resource), /.well-known/aauth-agent.json (agent), /.well-known/aauth-person.json (person server) and /.well-known/aauth-access.json (access server). \"This specification registers the following well-known URIs per [RFC8615]:\" \"Published at /.well-known/aauth-resource.json. A resource MAY publish this document\" [4]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/draft-hardt-oauth-aauth-protocol/", "last_verified": "2026-10-29", "freshness": "current" }, "cloudflare-pay-per-crawl": { "id": "cloudflare-pay-per-crawl", "name": "Cloudflare Pay Per Crawl", "acronym": null, "step": "pay", "phase": "candidate", "native_status": "Closed beta (as of 2026-07-28), launched as a private beta on 2025-07-01", "current_version": "closed beta", "version_date": "2026-07-28", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/", "last_verified": "2026-10-29", "freshness": "current" }, "wimse-agent-audit-record": { "id": "wimse-agent-audit-record", "name": "An Audit Record Format for AI Agent Authorization Decisions", "acronym": "Agent Audit Record", "step": "account", "phase": "draft", "native_status": "\"Active Internet-Draft (individual)\"; \"IESG state I-D Exists\" [2]. \"This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.\" is Datatracker's own wording [2]. The draft says \"Intended status: Standards Track\" [1]. The draft states its target: \"Its target is the AUDIT BoF and the working group it proposes.\" [1].", "current_version": "draft-gilda-audit-agent-audit-record-02", "version_date": "2026-10-27", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://www.ietf.org/archive/id/draft-gilda-audit-agent-audit-record-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "mcp-server-cards": { "id": "mcp-server-cards", "name": "MCP Server Cards", "acronym": "SEP-2127", "step": "discover", "phase": "stable", "native_status": "SEP-2127 Final [1]. History: SEP-1649 opened 2025-10-14 and moved to pull request #2127 on 2026-01-21 [3][2]; refactored into an Extensions Track charter, with the wire format moved to the ext-server-card repository, merged 2026-06-26 [4][5]; Core Maintainers voted to accept on 2026-08-13 and #2127 merged on 2026-10-06 [2]. When checked, the extension README still said \"Experimental\" [5] and the Server Card WG page still listed SEP-2127 as Draft [9]", "current_version": "Schema v1 (SEP-2127 Final)", "version_date": "2026-10-06", "canonical_path": "/mcp/server-card", "deprecated_paths": [ "/.well-known/mcp.json" ], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "SEP-2127 reserves GET /server-card as application/mcp-server-card+json. Although not a single fixed path in the static rule engine, probe, has, and validate_manifest check /mcp/server-card, /.well-known/mcp/server-card.json, and /.well-known/mcp.json live." }, "spec_url": "https://modelcontextprotocol.io/seps/2127-mcp-server-cards", "last_verified": "2026-10-28", "freshness": "current" }, "dawn-agent-discovery-framework": { "id": "dawn-agent-discovery-framework", "name": "A Framework for Agent Discovery in DAWN", "acronym": null, "step": "discover", "phase": "draft", "native_status": "Internet-Draft (draft-zhang-dawn-agent-discovery-framework-09), Intended Status: Informational; expires 2027-04-24", "current_version": "draft-zhang-dawn-agent-discovery-framework-09", "version_date": "2026-10-21", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-zhang-dawn-agent-discovery-framework-09", "last_verified": "2026-10-29", "freshness": "current" }, "agent-identity-document": { "id": "agent-identity-document", "name": "The Agent Identity Document: A Hosted, Accountable Public Record for AI Agents", "acronym": null, "step": "identify", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 13 April 2027", "current_version": "draft-alla-agent-identity-document-01", "version_date": "2026-10-10", "canonical_path": "/.well-known/agent-identity.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-alla-agent-identity-document-01", "last_verified": "2026-10-29", "freshness": "current" }, "mcp-dns-discovery": { "id": "mcp-dns-discovery", "name": "Discovery of Model Context Protocol Servers via DNS TXT Records", "acronym": null, "step": "discover", "phase": "draft", "native_status": "Active Internet-Draft (-09, Informational; expires 2027-04-25)", "current_version": "draft-morrison-mcp-dns-discovery-09", "version_date": "2026-10-22", "canonical_path": "_mcp.", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-morrison-mcp-dns-discovery-09", "last_verified": "2026-10-29", "freshness": "current" }, "agent-principal-binding": { "id": "agent-principal-binding", "name": "Security Principal and Verifier Binding for Agent Communication Protocols", "acronym": null, "step": "identify", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 17 April 2027", "current_version": "draft-bu-agentproto-security-principal-binding-08", "version_date": "2026-10-14", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-bu-agentproto-security-principal-binding-08", "last_verified": "2026-10-29", "freshness": "current" }, "aip-delegation-chain": { "id": "aip-delegation-chain", "name": "Agent Identity Protocol (AIP): Verifiable Delegation for AI Agent Systems", "acronym": "AIP", "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track; expires 13 April 2027", "current_version": "draft-prakash-aip-02", "version_date": "2026-10-10", "canonical_path": "/.well-known/aip/.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-prakash-aip-02", "last_verified": "2026-10-29", "freshness": "current" }, "credential-delegation-protocol-wimse": { "id": "credential-delegation-protocol-wimse", "name": "Credential Delegation Protocol for AI Agents in Multi-System Environments", "acronym": null, "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track; expires 16 April 2027", "current_version": "draft-sweeney-wimse-credential-delegation-01", "version_date": "2026-10-13", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-sweeney-wimse-credential-delegation-01", "last_verified": "2026-10-29", "freshness": "current" }, "agent-delegation-receipts": { "id": "agent-delegation-receipts", "name": "Agent Delegation Receipts", "acronym": null, "step": "permit", "phase": "draft", "native_status": "Internet-Draft (draft-nelson-agent-delegation-receipts-15), Intended Status: Informational; expires 2027-04-25", "current_version": "draft-nelson-agent-delegation-receipts-15", "version_date": "2026-10-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-nelson-agent-delegation-receipts-15", "last_verified": "2026-10-29", "freshness": "current" }, "aauth-r3": { "id": "aauth-r3", "name": "AAuth Rich Resource Requests", "acronym": "R3", "step": "permit", "phase": "draft", "native_status": "Exploratory Draft (-00); no known implementations", "current_version": "draft-hardt-aauth-r3-00", "version_date": "2026-09-28", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-hardt-aauth-r3-00", "last_verified": "2026-10-29", "freshness": "current" }, "acip": { "id": "acip", "name": "Agent Context Interchange Protocol", "acronym": "ACIP", "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 15 April 2027; work in progress", "current_version": "draft-agarwal-acip-00", "version_date": "2026-10-12", "canonical_path": ".agents/agent-context.yaml", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-agarwal-acip-00", "last_verified": "2026-10-29", "freshness": "current" }, "knowledge-linkset": { "id": "knowledge-linkset", "name": "The 'knowledge-linkset' Well-Known URI for Publishing Knowledge Artefacts", "acronym": null, "step": "discover", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 17 April 2027; work in progress", "current_version": "draft-besleaga-agentic-knowledge-wellknown-01", "version_date": "2026-10-14", "canonical_path": "/.well-known/knowledge-linkset", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-besleaga-agentic-knowledge-wellknown-01", "last_verified": "2026-10-29", "freshness": "current" }, "scitt-ai-agent-execution": { "id": "scitt-ai-agent-execution", "name": "AI Agent Execution Profile of SCITT", "acronym": "AIR", "step": "account", "phase": "draft", "native_status": "Revision `-01` published 12 October 2026 (35 pages, expires 15 April 2027), following `-00` (posted 11 April 2026, header dated 13 April 2026, 25 pages) [1][2][3][4][5]", "current_version": "draft-emirdag-scitt-ai-agent-execution-01 (air-1.0 / EES v0.1)", "version_date": "2026-10-12", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://www.ietf.org/archive/id/draft-emirdag-scitt-ai-agent-execution-01.txt", "last_verified": "2026-10-29", "freshness": "current" }, "agent-channel-fan-out": { "id": "agent-channel-fan-out", "name": "Agent-Channel Frame for Identity-Keyed Fan-Out Delivery to Concurrent Sessions", "acronym": null, "step": "coordinate", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 26 April 2027", "current_version": "draft-morrison-agent-channel-fan-out-03", "version_date": "2026-10-23", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-morrison-agent-channel-fan-out-03", "last_verified": "2026-10-29", "freshness": "current" }, "aagv": { "id": "aagv", "name": "Agentic Authority Graph Validation", "acronym": "AAGV", "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Experimental; expires 17 April 2027", "current_version": "draft-watts-agentic-authority-graph-validation-00", "version_date": "2026-10-14", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-watts-agentic-authority-graph-validation-00", "last_verified": "2026-10-29", "freshness": "current" }, "agentic-payments-gating-model": { "id": "agentic-payments-gating-model", "name": "Agent-Initiated Payment Gating", "acronym": null, "step": "pay", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 11 April 2027", "current_version": "draft-king-yew-choo-agentic-payments-01", "version_date": "2026-10-08", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01", "last_verified": "2026-10-29", "freshness": "current" }, "idmandat-credential": { "id": "idmandat-credential", "name": "ID MANDAT: A Machine-Readable Credential for the Agents of a Company", "acronym": "ID MANDAT", "step": "identify", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; individual submission describing a deployed beta (version 0.3), not the product of an IETF working group", "current_version": "draft-koenig-idmandat-credential-00", "version_date": "2026-10-16", "canonical_path": "/.well-known/idmandat.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-koenig-idmandat-credential-00", "last_verified": "2026-10-29", "freshness": "current" }, "lws10-authn-ssi-cid": { "id": "lws10-authn-ssi-cid", "name": "LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers", "acronym": "LWS-SSI-CID", "step": "identify", "phase": "draft", "native_status": "W3C Working Draft 15 October 2026; published by the Linked Web Storage Working Group as a Working Draft using the Recommendation track. The page also says: This is an unofficial proposal.", "current_version": "W3C Working Draft", "version_date": "2026-10-15", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://www.w3.org/TR/lws10-authn-ssi-cid/", "last_verified": "2026-10-29", "freshness": "current" }, "wimse-workload-identity-metadata": { "id": "wimse-workload-identity-metadata", "name": "Workload Identity Metadata", "acronym": null, "step": "identify", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track; expires 19 April 2027", "current_version": "draft-heigh-wimse-workload-identity-metadata-00", "version_date": "2026-10-16", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-heigh-wimse-workload-identity-metadata-00", "last_verified": "2026-10-29", "freshness": "current" }, "haace": { "id": "haace", "name": "High-Assurance Agent Control Envelope", "acronym": "HAACE", "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Informational; expires 18 April 2027", "current_version": "draft-watts-high-assurance-agent-control-envelope-00", "version_date": "2026-10-15", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-watts-high-assurance-agent-control-envelope-00", "last_verified": "2026-10-23", "freshness": "current" }, "local-tool-call-proof": { "id": "local-tool-call-proof", "name": "Per-Call Proof for Local Tool Invocation by AI Agents", "acronym": null, "step": "permit", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track; expires 15 April 2027", "current_version": "draft-lee-wimse-local-tool-call-proof-01", "version_date": "2026-10-12", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-lee-wimse-local-tool-call-proof-01", "last_verified": "2026-10-29", "freshness": "current" }, "agent-authorization-envelope": { "id": "agent-authorization-envelope", "name": "Agent Authorization Envelope", "acronym": "AAE", "step": "permit", "phase": "draft", "native_status": "Active Internet-Draft (-02, expires 2027-03-10)", "current_version": "draft-kroehl-agentic-trust-aae-02", "version_date": "2026-09-06", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-kroehl-agentic-trust-aae-02", "last_verified": "2026-10-29", "freshness": "current" }, "a2wp": { "id": "a2wp", "name": "Agent-to-Wallet Protocol for Digital Credentials", "acronym": "A2WP", "step": "present", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Standards Track; expires 20 April 2027; work in progress", "current_version": "draft-senarath-a2wp-01", "version_date": "2026-10-17", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-senarath-a2wp-01", "last_verified": "2026-10-29", "freshness": "current" }, "agent-decision-commitment": { "id": "agent-decision-commitment", "name": "Agent Decision Commitments for Payments", "acronym": "ADC", "step": "account", "phase": "draft", "native_status": "Internet-Draft, Intended Status: Experimental; expires 18 April 2027", "current_version": "draft-milan-agent-decision-commitment-00", "version_date": "2026-10-15", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "candidate record; probe rule pending" }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-milan-agent-decision-commitment-00", "last_verified": "2026-10-29", "freshness": "current" }, "gbz-185-agent-interconnection": { "id": "gbz-185-agent-interconnection", "name": "GB/Z 185 Artificial intelligence — Agent interconnection", "acronym": "GB/Z 185", "step": "coordinate", "phase": "stable", "native_status": "In force. \"标准状态： 现行\" (standard status: in force) [3]. The search API lists \"total\":7 records, each like \"C_STD_CODE\":\"GB/Z 185.5-2026\",\"STD_NATURE\":\"指导性技术文件\",\"STATE\":\"现行\",\"ISSUE_DATE\":\"2026-05-22\" [2]. Effective on publication: \"拟实施日期：发布即实施。\" (planned implementation date: on publication) [4]. Two more parts are being drafted: 20264195-Z-469 正在起草 (Part 8, agent audit) [5] and 20264253-Z-469 正在起草 (Part 9, agent transaction) [6]", "current_version": "GB/Z 185.1-2026 to GB/Z 185.7-2026", "version_date": "2026-05-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "probe rule pending: Part 5 (discovery) full text not yet read for a well-known path" }, "spec_url": "https://openstd.samr.gov.cn/bzgk/std/newGbInfo?hcno=CFF03D872963466AC7F03ED0E28B6702", "last_verified": "2026-10-29", "freshness": "current" }, "amp-ant": { "id": "amp-ant", "name": "Agentic Mobile Protocol (AMP)", "acronym": "AMP", "step": "pay", "phase": "draft", "native_status": "Published and open-sourced, but no numbered release. Repository last push `\"pushed_at\": \"2026-09-23T06:32:45Z\"` [7]; no tags or releases when checked. The reference code is a local demo: \"per-run SQLite / JSON stores under `.temp-db/`\" [6]", "current_version": "Unversioned (main branch)", "version_date": "2026-09-23", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "AMP mandates and payment tokens are exchanged inside an authorised wallet flow; nothing is published at a fixed path." }, "spec_url": "https://github.com/ant-intl/AMP/blob/main/docs/Overview.md", "last_verified": "2026-10-29", "freshness": "current" }, "x401": { "id": "x401", "name": "x401: HTTP Proof Requirement Protocol", "acronym": null, "step": "identify", "phase": "draft", "native_status": "Status: Draft, Version: 0.2.0 (\"The spec is a working draft\"; repo has no tags or releases; Proof calls its own Verifier service live in production with Cloudflare Workers) [1][3][4][14]", "current_version": "0.2.0 (Draft, bumped 2026-06-22; v0.1.0 still published at /spec/0.1.0/)", "version_date": "2026-06-22", "canonical_path": "none — signalled per request on the protected route itself [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "A PROOF-REQUEST header appears only on a resource that asks for proof; there is no fixed path to check." }, "spec_url": "https://x401.proof.com/spec/latest/", "last_verified": "2026-10-29", "freshness": "current" }, "kya-os": { "id": "kya-os", "name": "KYA-OS (Know Your Agent Operating System)", "acronym": "KYA-OS", "step": "identify", "phase": "stable", "native_status": "Self-declared stable and ratified; DIF approval reported but no public ratification record found. Spec: \"Status: Stable\" \"Donated to DIF TAAWG (Decentralized Identity Foundation, Trusted AI Agents Working Group) and ratified as a DIF standard.\" [1]. Task-force notes, 21 July 2026: \"Grace: spec was approved by SC, next step is to announce on the blog (avoid being repetitive).\" [13]. DIF newsletter, 2026-08-18: \"Check out the mention of the KYA-OS approval in Business Wire!\" [15]", "current_version": "1.0.0", "version_date": "2026-07-29", "canonical_path": "/.well-known/kya-os-card.json on a bare did:web host, served live by the reference demo server [2][19]. The spec also says \"KYA-OS servers SHOULD expose `/.well-known/mcp`.\" [1], but the reference server returned 404 there on 2026-10-29", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/mcp", "expect": { "json_keys": [ "serverDid" ] }, "note": "KYA-OS SPEC.md section 10: servers SHOULD expose /.well-known/mcp with serverDid and capabilities." }, "spec_url": "https://raw.githubusercontent.com/decentralized-identity/kya-os-mcp/main/SPEC.md", "last_verified": "2026-10-29", "freshness": "current" }, "kyapay-token": { "id": "kyapay-token", "name": "KYAPay Token", "acronym": "KYAPay", "step": "pay", "phase": "draft", "native_status": "Active Internet-Draft, not adopted, not an RFC: \"IESG state I-D Exists\" [2]. `\"expires\": \"2027-04-05T00:52:13Z\"` [4]. The predecessor is \"Replaced Internet-Draft (individual) Expired & archived\" and \"IESG state Replaced by draft-skyfire-oauth-kyapay-token\" [6]. Five companion drafts cover use, token exchange and claim values [11][10]. The JWT claims, media types and the jwks.json well-known suffix it asks IANA to register were not in the IANA registries on 2026-10-29 [1][37][38][39]", "current_version": "draft-skyfire-oauth-kyapay-token-02, dated 2 October 2026 in its header, \"Expires: 5 April 2027\" [1]; API `\"rev\": \"02\"` [4]. Posted (UTC) 2026-07-05 (-00), 2026-07-19 (-01) and 2026-10-02 (-02) [5]; the Datatracker history shows -02 as \"2026-10-01 02 Michael Jones New version available: draft-skyfire-oauth-kyapay-token-02.txt\" because it displays Pacific time [3]. A newer editor's copy, \"Published: 28 October 2026\", has not been submitted [8]", "version_date": "2026-10-02", "canonical_path": "/.well-known/jwks.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "KYAPay tokens are presented per request by the agent; nothing is published at a fixed path on the resource server." }, "spec_url": "https://www.ietf.org/archive/id/draft-skyfire-oauth-kyapay-token-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "oauth-cimd": { "id": "oauth-cimd", "name": "OAuth Client ID Metadata Document", "acronym": "CIMD", "step": "permit", "phase": "working-group", "native_status": "Active Internet-Draft, WG Document of the IETF oauth WG; -02 dated 2026-07-06, expires 2027-01-07; the draft header says Standards Track", "current_version": "draft-ietf-oauth-client-id-metadata-document-02", "version_date": "2026-07-06", "canonical_path": "/.well-known/oauth-authorization-server", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/oauth-authorization-server", "expect": { "json_keys": [ "client_id_metadata_document_supported" ] }, "note": "RFC 8414 metadata advertises CIMD support with client_id_metadata_document_supported." }, "spec_url": "https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "iab-comp": { "id": "iab-comp", "name": "CoMP (Content Monetization Protocols)", "acronym": "CoMP", "step": "permit", "phase": "stable", "native_status": "CoMP v1 (Final): open for public comment until 2026-04-09 and finalized 2026-04-28, per IAB Tech Lab's initiative page", "current_version": "CoMP v1 (Final)", "version_date": "2026-04-28", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "CoMP defines request and response objects, not a fixed path; supply discovery is out of scope." }, "spec_url": "https://github.com/IABTechLab/CoMP/blob/main/CoMP-1.0.md", "last_verified": "2026-10-29", "freshness": "current" }, "agent-commerce-kit": { "id": "agent-commerce-kit", "name": "Agent Commerce Kit (ACK)", "acronym": "ACK", "step": "pay", "phase": "draft", "native_status": "Version 1 is \"Current\" by ACK's own scheme; a v2 redesign is an open draft proposal. \"The current stable protocol version is 2025-05-04.\" [8] \"Status: proposal. Nothing here has shipped.\" [9] Pull request #179 is open (draft: true), opened 2026-08-27, last updated 2026-10-17 (UTC) [10].", "current_version": "2025-05-04 (agentcommercekit@0.11.0)", "version_date": "2026-08-04", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "ACK identity and payment objects are exchanged between parties; no fixed path is defined." }, "spec_url": "https://www.agentcommercekit.com/overview/concepts.md", "last_verified": "2026-10-29", "freshness": "current" }, "cloudflare-markdown-for-agents": { "id": "cloudflare-markdown-for-agents", "name": "Markdown for Agents", "acronym": null, "step": "read", "phase": "living", "native_status": "Beta; free on Pro, Business and Enterprise plans and for SSL for SaaS customers [1][2]", "current_version": "No numbered versions; docs last updated 2026-10-09 [1]", "version_date": "", "canonical_path": "Any HTML page on an enabled zone, requested with Accept: text/markdown; enabled in AI Crawl Control, by a Configuration Rule or through the content_converter zone setting [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Needs an Accept: text/markdown request header on any page; although skipped in static rule evaluation, probe, has, and validate_manifest observe it live on GET / with Accept: text/markdown." }, "spec_url": "https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/", "last_verified": "2026-10-28", "freshness": "current" }, "otel-genai-semconv": { "id": "otel-genai-semconv", "name": "OpenTelemetry GenAI Semantic Conventions (agents and MCP)", "acronym": null, "step": "account", "phase": "draft", "native_status": "Status: Development (OpenTelemetry document status) on both the agent-spans and MCP documents; the repository has no tagged release", "current_version": "Development (unreleased; repository has no tags); builds on core semantic conventions v1.44.0", "version_date": "2026-10-19", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "Telemetry naming conventions inside an operator's tracing pipeline; no origin artefact." }, "spec_url": "https://github.com/open-telemetry/semantic-conventions-genai/blob/main/docs/gen-ai/gen-ai-agent-spans.md", "last_verified": "2026-10-23", "freshness": "current" }, "erc-8001": { "id": "erc-8001", "name": "ERC-8001: Agent Coordination Framework", "acronym": "ERC-8001", "step": "coordinate", "phase": "stable", "native_status": "Final Standards Track ERC (moved to Last Call 2025-12-02 and to Final 2025-12-16)", "current_version": "Final, created 2025-08-02", "version_date": "2025-12-16", "canonical_path": "none — no well-known file; discovery is by contract address/ABI", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "An Ethereum contract; observable via eth_call, not HTTP." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8001", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8126": { "id": "erc-8126", "name": "ERC-8126: AI Agent Verification", "acronym": "ERC-8126", "step": "identify", "phase": "stable", "native_status": "Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft", "current_version": "Final, created 2026-01-15", "version_date": "2026-06-02", "canonical_path": "none — no well-known file; discovery is by contract address/ABI", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "An Ethereum contract; observable via eth_call, not HTTP." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8126", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8196": { "id": "erc-8196", "name": "ERC-8196: AI Agent Authenticated Wallet", "acronym": "ERC-8196", "step": "permit", "phase": "stable", "native_status": "Final Standards Track ERC (Final 2026-07-21); requires ERC-4337 and ERC-8126", "current_version": "Final, created 2026-03-14", "version_date": "2026-07-21", "canonical_path": "none — no well-known file; discovery is by contract address/ABI", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "not-http", "note": "An Ethereum contract; observable via eth_call, not HTTP." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8196", "last_verified": "2026-10-29", "freshness": "current" }, "erc-8444": { "id": "erc-8444", "name": "ERC-8444: Agentic Resource Discovery (ARD) Onchain", "acronym": "ERC-8444", "step": "discover", "phase": "draft", "native_status": "Draft Standards Track ERC, created 2026-10-12", "current_version": "Draft, created 2026-10-12", "version_date": "2026-10-12", "canonical_path": "/.well-known/ard.json", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "path": "/.well-known/ard.json", "expect": { "text_match": "\"value:controllers?\"" }, "note": "A domain acknowledges an ERC-8444 controller address with value:controllers or value:controller in its ARD manifest." }, "spec_url": "https://eips.ethereum.org/EIPS/eip-8444", "last_verified": "2026-10-29", "freshness": "current" }, "jafar": { "id": "jafar", "name": "JAFAR: A JSON-Based Format for Publishing IP Ranges of Automated HTTP Clients", "acronym": "JAFAR", "step": "identify", "phase": "draft", "native_status": "Active Internet-Draft (draft-illyes-webbotauth-jafar-01), Intended Status: Informational; expires 2027-04-25", "current_version": "draft-illyes-webbotauth-jafar-01", "version_date": "2026-10-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "The draft defines the JSON format only, not where the file is published." }, "spec_url": "https://datatracker.ietf.org/doc/html/draft-illyes-webbotauth-jafar-01", "last_verified": "2026-10-29", "freshness": "current" }, "anonymous-bot-auth": { "id": "anonymous-bot-auth", "name": "Anonymous Bot Authentication", "acronym": "ABA", "step": "identify", "phase": "draft", "native_status": "Active Internet-Draft, Intended Status: Informational; expires 20 January 2027; the draft says it 'has not yet seen significant security analysis'", "current_version": "draft-rescorla-anonymous-webbotauth-01", "version_date": "2026-07-19", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Anonymous credentials are presented per request; no site-side artefact is defined." }, "spec_url": "https://datatracker.ietf.org/doc/draft-rescorla-anonymous-webbotauth/", "last_verified": "2026-10-29", "freshness": "current" }, "workload-authz-grant": { "id": "workload-authz-grant", "name": "Workload Authorization Grant (WAG)", "acronym": "WAG", "step": "permit", "phase": "draft", "native_status": "\"Active Internet-Draft (individual)\"; \"IESG state I-D Exists\" [1]. \"This document is an early, exploratory individual draft, published to solicit discussion of the deployment pattern it describes. It is not a working group document, does not describe a shipped or committed design, and does not represent a position or roadmap of the editors' employers.\" [5]. oauth.net: \"WAG is an individual draft and an early exploration, not yet an OAuth Working Group item.\" [20]", "current_version": "draft-carleton-workload-authz-grant-01", "version_date": "2026-09-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "The Workload Authorization Grant is a platform-signed JWT presented at a token endpoint; nothing is published at a fixed path." }, "spec_url": "https://datatracker.ietf.org/doc/draft-carleton-workload-authz-grant/", "last_verified": "2026-10-29", "freshness": "current" }, "oauth-id-continuation": { "id": "oauth-id-continuation", "name": "Identity Continuation Assertion for OAuth 2.0 Token Exchange", "acronym": null, "step": "permit", "phase": "draft", "native_status": "\"Active Internet-Draft (individual)\"; \"IESG state I-D Exists\" [2]. \"This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.\" is Datatracker's own wording [2]. The draft says \"Intended status: Standards Track\" [1]. Its header line reads \"Web Authorization Protocol K. McGuinness\", and it says \"Discussion of this document takes place on the Web Authorization Protocol Working Group mailing list\" [1]. That routes discussion to a working-group mailing list; it does not make the draft a working-group document, and Datatracker files it as individual [2].", "current_version": "draft-mcguinness-oauth-id-continuation-assertion-02", "version_date": "2026-09-09", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "needs-credentials", "note": "The identity-continuation assertion is a token-exchange subject token; it is not published at a fixed path." }, "spec_url": "https://www.ietf.org/archive/id/draft-mcguinness-oauth-id-continuation-assertion-02.txt", "last_verified": "2026-10-29", "freshness": "current" }, "oauth-agent-delegation": { "id": "oauth-agent-delegation", "name": "An Attenuated Delegation Profile for Automated Agents", "acronym": null, "step": "permit", "phase": "draft", "native_status": "\"Active Internet-Draft (individual)\"; \"IESG state I-D Exists\" [2]. \"This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.\" is Datatracker's own wording [2]. The draft says \"Intended status: Standards Track\" [1]. Its first header line reads \"Web Authorization Protocol A. Hassan\" [1]. That header line does not make it a working-group document: Datatracker files it as individual, as above [2].", "current_version": "draft-hamr-oauth-agent-delegation-03", "version_date": "2026-10-22", "canonical_path": null, "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Agent-Delegation is an HTTP header on a request signed with RFC 9421; there is no fixed path to fetch." }, "spec_url": "https://www.ietf.org/archive/id/draft-hamr-oauth-agent-delegation-03.txt", "last_verified": "2026-10-29", "freshness": "current" }, "opena2a-aap": { "id": "opena2a-aap", "name": "OpenA2A Agent Authorization Protocol", "acronym": "AAP", "step": "permit", "phase": "draft", "native_status": "See IETF tracker.", "current_version": "draft-fane-opena2a-aap-02", "version_date": "2026-10-02", "canonical_path": "No well-known path. The draft asks IANA for a URI scheme: \"This document requests registration of the “aap” URI scheme in the Uniform Resource Identifier (URI) Schemes registry\" [1]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "OpenA2A AAP is a token model. The named broker layer is not specified, and nothing is published at a fixed path." }, "spec_url": "https://datatracker.ietf.org/doc/draft-fane-opena2a-aap/", "last_verified": "2026-10-30", "freshness": "current" }, "open-responses": { "id": "open-responses", "name": "Open Responses", "acronym": "Open Responses", "step": "act", "phase": "stable", "native_status": "Published, date-versioned specification; current release 2026-04-24 [3][9]. The home page, specification and changelog carry no beta, preview or general-availability label (checked 2026-10-29) [2][1][3]. Compliance is defined by the spec: \"Any implementer can be considered to have a Open Responses-compliant API if they have an API that implements this spec directly or is a proper superset of Open Responses.\" [1]. The project publishes a test suite: \"Test any API endpoint for Open Responses specification compliance. Configure your connection details and run the test suite to validate responses against the OpenAPI schema.\" [5]", "current_version": "2026-04-24", "version_date": "2026-04-24", "canonical_path": "No discovery file. Each implementer serves the endpoint on its own host, for example OpenRouter at \"https://openrouter.ai/api/v1/responses\" [15]; Databricks uses its own path: \"Send requests to the /serving-endpoints/open-responses path with the model serving endpoint name in the model field of the request body.\" [16]", "deprecated_paths": [], "superseded_by": null, "probe_rule": { "skip": "no-fixed-path", "note": "Open Responses defines the /v1/responses inference and tool-calling API schema rather than a public root discovery manifest." }, "spec_url": "https://www.openresponses.org/specification", "last_verified": "2026-10-29", "freshness": "current" } } }