All articles
184 articles across nine categories, plus general terms. Every cell has a source or says it does not. JSON · CSV · how rows get here
step
implementation
| Title | Category | Type | Status | Governed by |
|---|---|---|---|---|
| Agent Attribution Protocol | Account | Protocol | "The open standard for AI agent affiliate attribution" (vendor's own description); v1.0 spec published, centrally operated | Single vendor (Rako); the spec text is published under Apache-2.0, but issuance, verification and settlement are centrally operated by Rako, which the spec calls the 'Protocol Authority' |
| Agent Audit Trail | Account | Protocol | Active Internet-Draft (individual submission), Intended status: Standards Track; not a Working Group document | Individual IETF Internet-Draft (`Intended status: Standards Track`, `IESG state: I-D Exists`, not endorsed by the IETF and not adopted by a Working Group); latest revision `-09` published 26 October 2026 (expires 29 April 2027), following `-00` (29 March 2026), `-01` (19 August 2026), `-02` (3 September 2026), `-03` (5 September 2026), `-04` (15 September 2026), `-05` (25 September 2026), `-06` (29 September 2026), `-07` (11 October 2026), and `-08` (13 October 2026) [1][2][3][4][5][6][7][8][9] |
| Agent Decision Commitments for Payments | Account | Protocol | Internet-Draft, Intended Status: Experimental; expires 18 April 2027 | Individual Internet-Draft; discussion on DISPATCH, SCITT and OAuth mailing lists |
| Agentic EoR (Employer / Entity of Record) | Account | Term | ||
| AI Agent Execution Profile of SCITT | Account | Protocol | 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] | Individual IETF Internet-Draft (`Intended status: Informational`, `IESG state: I-D Exists`, not endorsed by the IETF and not adopted by a Working Group); companion `Evidence Envelope Specification v0.1` (`EES v0.1`) maintained by Veridic Inc. [1][2][3][7] |
| An Audit Record Format for AI Agent Authorization Decisions | Account | Protocol | "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]. | IETF individual Internet-Draft targeting the proposed AUDIT BoF / working group (replaces draft-gilda-wimse-agent-audit-record) |
| Audit record | Account | Term | ||
| OpenTelemetry GenAI Semantic Conventions (agents and MCP) | Account | Protocol | Status: Development (OpenTelemetry document status) on both the agent-spans and MCP documents; the repository has no tagged release | OpenTelemetry project (backed by the CNCF); developed in the open-telemetry/semantic-conventions-genai repository, which extends the core OpenTelemetry Semantic Conventions |
| Verifiable Intent | Account | Protocol | Draft (v0.1); open-sourced specification and reference implementation | Mastercard; contributed to the FIDO Alliance Payments TWG (2026-04-28); built on FIDO Alliance, EMVCo, IETF and W3C primitives |
| Verifiable Intent | Account | Term | ||
| Ad Context Protocol (AdCP) | Act | Protocol | 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] | AgenticAdvertising.org. "AdCP is a project of AgenticAdvertising.org, an industry organization of publishers, platforms, agencies, and technology providers advancing open standards for AI-powered advertising." [1]. "AgenticAdvertising.org is a Delaware nonprofit nonstock corporation, founded in 2025 and intended to qualify under Section 501(c)(6)." [20]. Its directors "adopted the current bylaws by unanimous written consent on June 11, 2026, subject to voting member ratification." [19]; "Benjamin Masse was named Board President in the September 2026 announcement." [20]. The repository charter and the docs FAQ still describe an interim board to be replaced on May 6, 2026 [17][18] |
| Agent Client Protocol | Act | Protocol | 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] | Jointly by Zed and JetBrains under what the project calls "an interim governance model", "while working toward transitioning to an independent foundation" [4]. The lead maintainers are Ben Brandt (Zed Industries) and Sergey Ignatov (JetBrains), who make the final decisions; core maintainers can veto maintainers' decisions by majority vote, and maintainers, core maintainers and lead core maintainers together form the ACP steering group [4]. Changes go through a public Request for Dialog (RFD) process, whose page still says "The project currently has a design team with the Zed team as the lead (BDFL)." [6]. Apache 2.0 licence [4][17]; no Contributor License Agreement [4] |
| Agent Connect Protocol | Act | Protocol | 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] | AGNTCY, a Linux Foundation project since 2025-07-29 (formative members: Cisco, Dell Technologies, Google Cloud, Oracle, Red Hat; Apache-2.0, Copyright AGNTCY Contributors). The AGNTCY Core Working Group charter (last changed 2026-05-28) still lists ACP alongside OASF [1][5][6][7] |
| Agent Protocol | Act | Protocol | 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 | Originated as an AI Engineer Foundation (AIEF) community project (GitHub org formerly AI-Engineer-Foundation); the repository now lives under 'agi-inc' and states it is 'Maintained by AGI, Inc.', a commercial entity; the docs domain linked from the repository, agentprotocol.ai, currently serves unrelated third-party content rather than AIEF/AGI Inc. project documentation |
| Agent skill | Act | Term | ||
| Agent Skills | Act | Protocol | 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] | Agentic AI Foundation (AAIF), under the Linux Foundation, since 2026-10-22, when Anthropic contributed the standard as an AAIF project [7][8]. Anthropic handed over the name and logo, the GitHub organization and the agentskills.io domain [7]. A multi-company Technical Steering Committee guides the project [9]; engineers from Anthropic, Google, OpenAI and other companies maintain it as individuals, with David Soria Parra and Mahesh Murag as Lead Maintainers [7] |
| Agentic Real Time Framework | Act | Protocol | Final v1.0 specification, published after public comment; v2.0 development already underway | IAB Tech Lab (non-profit standards consortium); Agentic Task Force working group |
| agents.json | Act | Protocol | 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] | Wildcard AI (wild-card-ai/agents-json); MAINTAINERS.md lists Yagnya Patel (yagnyaPatel) as current maintainer ("Maintainer GitHub ID Affiliation Yagnya Patel yagnyaPatel Indpendent") [8], and the README notes: "This GitHub repository will host informal reviews, allowing for version control and public discussion." [1] |
| Elicitation | Act | Term | ||
| Idempotency-Key header | Act | Term | ||
| MCP | Act | Term | ||
| MCP Prompt | Act | Term | ||
| Model Context Protocol | Act | Protocol | Active open protocol. 2026-07-28 is the current revision [2]. Code and specifications are released under the Apache License 2.0 [10] | Agentic AI Foundation (AAIF), a directed fund under the Linux Foundation, since 2025-12-09 [12][13]. MCP is set up as a Series of LF Projects, LLC. Technical decisions rest with its maintainers, and the Lead Maintainers have final say [10] |
| NLWeb | Act | Protocol | 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] | The nlweb-ai GitHub organization, with Microsoft ties still in place. The project moved its repository there: "We've migrated the repository from microsoft/NLWeb to our new independent GitHub organization at NLWeb-ai." The stated aim: "A neutral space where contributors from any company or background can collaborate" [7]. On 2026-10-29 github.com/microsoft/NLWeb answered HTTP 301 to github.com/nlweb-ai/NLWeb. The licence still reads "MIT License Copyright (c) Microsoft Corporation." [5], and the README's support contact, "For questions about this GitHub project, please contact NLWeb Support.", is the address NLWebSup@microsoft.com [3]. No foundation holds the project. A W3C Community Group exists: "Posted on: October 20, 2025 The NLWeb Community Group has been launched:" "This is a community initiative. This group was originally proposed on 2025-10-16 by Ramanathan Guha." "W3C's hosting of this group does not imply endorsement of the activities." Its page lists "Chairs None yet" [8] |
| Open Responses | Act | Protocol | 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] | Open Responses a Series of LF Projects, LLC, a project of the Agentic AI Foundation at the Linux Foundation: "Technical Charter (the "Charter") for Open Responses a Series of LF Projects, LLC Adopted October 21, 2026"; the TSC Chair is the "primary communication contact between the Project and Agentic AI Foundation (AAIF), a directed fund of The Linux Foundation." [4]. "The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project. The TSC voting members are initially the Project's Maintainers." [4]. The CONTRIBUTING file names 9 maintainers: "The Maintainers are the initial voting members of the Technical Steering Committee (TSC). - Steve Coffey, OpenAI - Ankit Mathur, Databricks - Anthony Liguori, Amazon - Ben Burtenshaw, HuggingFace - Devon Rifkin, Ollama - Ji Huang, OpenAI - Matt Apperson, OpenRouter - Shaun Smith, HuggingFace - Kedar Thakker, Ramp" [6]. The move was announced on 2026-10-22: "SAN JOSE, Oct. 22, 2026 – The Agentic AI Foundation (AAIF), today announced four new projects: Agent Skills, contributed by Anthropic; Open Responses, contributed by OpenAI; OpenEnv, contributed by Hugging Face; and OpenSandbox, contributed by Alibaba." [11] |
| OpenAI Apps SDK manifests | Act | Protocol | 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 | OpenAI (single vendor) for the ChatGPT-only parts: the `openai/*` metadata keys, the `window.openai` bridge, review and the directory [2][9]. The UI layer follows MCP Apps, an extension of the Model Context Protocol [1][20]. The package format follows Agent Plugins: "Its initial Technical Steering Committee includes Core Maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel." [21] |
| Origin trial | Act | Term | ||
| Sampling | Act | Term | ||
| SKILL.md | Act | Term | ||
| Streamable HTTP | Act | Term | ||
| Tool | Act | Term | ||
| Web Agent Protocol (WAP) | Act | Protocol | Dormant: last commit 2025-06-03 | Single company (OTA Tech AI); MIT-licensed public GitHub repository; no independent standards process or multi-party governance found |
| WebMCP | Act | Protocol | 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] | W3C Web Machine Learning Community Group, in the webmachinelearning/webmcp GitHub repository (created 2025-08-05) [2]. Editors: Brandon Walderman and Samuel Dallstream (Microsoft), Khushal Sagar and Dominic Farolino (Google) [1] |
| A2A Task | Coordinate | Term | ||
| Agent Communication Protocol | Coordinate | Protocol | "ACP is now part of A2A under the Linux Foundation" (repository banner) | Formerly IBM BeeAI; archived, functionality merged into A2A under the Linux Foundation |
| Agent Interaction & Transaction Protocol (AITP) | Coordinate | Protocol | 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] | NEAR AI, through its nearai/aitp GitHub repository under the MIT licence (`"spdx_id": "MIT"`) [9]. "AITP is a spec in progress and we are open to comments, feedback, and contributions!" [1]. No standards-body process was found |
| Agent Network Protocol | Coordinate | Protocol | Released v1.2 (core suite); meta-protocol (ANP-06) remains draft/unreleased | Community-led open-source project (agent-network-protocol GitHub org) |
| Agent Transfer Protocol | Coordinate | Protocol | Internet-Draft (work in progress), independent submission | IETF individual/independent submission; not adopted by an IETF working group |
| Agent-Channel Frame for Identity-Keyed Fan-Out Delivery to Concurrent Sessions | Coordinate | Protocol | Internet-Draft, Intended Status: Informational; expires 26 April 2027 | Individual Internet-Draft by a single author, submitted via the IETF datatracker; not an IETF working group document. Datatracker lists one IPR disclosure (No. 7363, posted 2026-06-22, holder Alter Meridian Pty Ltd) covering revision -00. |
| Agent2Agent (A2A) | Coordinate | Term | ||
| Agent2Agent Protocol (A2A) | Coordinate | Protocol | Stable: v1.0 is "the first stable specification" [9] | Linux Foundation: launched as the Agent2Agent (A2A) project on 2025-06-23, seeded with Google's transfer of the specification, SDKs and tooling [6][7]. Since August 2026 a Growth Stage project of the Agentic AI Foundation (AAIF), a Linux Foundation-directed foundation that also hosts MCP: the AAIF Technical Committee approved it on 2026-07-15, the Governing Board on 2026-08-04, and AAIF announced it on 2026-08-17 [10][9][11]. Within the project, a Technical Steering Committee of nine seats held by Google, Microsoft, Cisco, Amazon Web Services, Salesforce, ServiceNow, SAP, IBM and Bloomberg [8] |
| Agentic Advertising Management Protocols | Coordinate | Protocol | Active umbrella initiative, current release AAMP 2.3, described by its own authors as 'far more than a single framework' | IAB Tech Lab (non-profit standards consortium); Agentic Task Force working group |
| Agora Protocol | Coordinate | Protocol | 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. | The author group, with no foundation or standards body found. The Working Standard says "Copyright Notice (C) 2025 Samuele Marro." [3] The Python library has 2 contributors on GitHub (samuelemarro 133, ShayekhBinIslam 1 commits) [4]. "Our main community point is on Discord!" [5] |
| Coral Protocol (CoralOS) | Coordinate | Protocol | "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' | Single company/startup-led open-source project (GitHub org Coral-Protocol); rebranded 'CoralOS' (docs moved from docs.coralprotocol.org to docs.coralos.ai); not a multi-stakeholder standards body |
| ERC-8001: Agent Coordination Framework | Coordinate | Protocol | Final Standards Track ERC (moved to Last Call 2025-12-02 and to Final 2025-12-16) | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| GB/Z 185 Artificial intelligence — Agent interconnection | Coordinate | Protocol | 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] | Issued jointly by SAMR and the Standardization Administration of China (SAC): "发布单位 国家市场监督管理总局、国家标准化管理委员会" (issuing bodies: State Administration for Market Regulation, Standardization Administration of China) [3]. Committee: "国家标准《人工智能 智能体互联 第1部分：总体架构》 由 TC28 （全国信息技术标准化技术委员会）归口， TC28SC42 （全国信息技术标准化技术委员会人工智能分会）执行 ，主管部门为 国家标准委 。" (responsible committee TC28 (National Information Technology Standardization Technical Committee), executed by TC28/SC42 (its AI subcommittee), supervised by SAC) [1]. "本文件由全国信息技术标准化技术委员会（SAC/TC 28）提出并归口。" (proposed by and under SAC/TC 28) [15] |
| Natural Language Interaction Protocol (NLIP) | Coordinate | Protocol | 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] | Ecma International Technical Committee 56 (TC56). "TC56 operates under the Royalty-Free Patent Policy"; "Chair: Dinesh Verma (IBM) Vice-Chair: Elisa Bertino (Purdue University) Secretaries: Patrick Luthi (Ecma International) and Luyi Xing (University of Illinois)" [15]. Formal TC56 members, per the participants' paper (2026-09-03): "The members who officially joined Ecma TC56 to define the official standards included IBM," Hitachi, Red Hat, ServiceNow, Purdue University, Indiana University Bloomington, "University at Buffalo, Fordham University, Chicago State University, Marist University, and City University of New York." [17]. The University of Illinois joined Ecma later: "In June 2026, University of Illinois Urbana-Champaign was approved as a not-for-profit member" [31]. Ecma's own TC56 page does not list members [15] |
| Secure Low-Latency Interactive Messaging (SLIM) | Coordinate | Protocol | 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] | The AGNTCY project at the Linux Foundation (announced 2025-07-29; formative members: Cisco, Dell Technologies, Google Cloud, Oracle, Red Hat; 8-member Technical Steering Committee; 5 SLIM repository maintainers; Apache-2.0) [7][8][16][18][19] |
| Subagent | Coordinate | Term | ||
| A Framework for Agent Discovery in DAWN | Discover | Protocol | Internet-Draft (draft-zhang-dawn-agent-discovery-framework-09), Intended Status: Informational; expires 2027-04-24 | Individual IETF Internet-Draft (Datatracker: Active Internet-Draft (individual)) written for the scope of the IETF DAWN (Discovery of Agents With Names) working group; not a DAWN working-group document; Informational intended status |
| Agent Card | Discover | Term | ||
| Agent Directory Service | Discover | Protocol | Internet-Draft; work in progress; canonical spec tracked at spec.dir.agntcy.org | AGNTCY project (github.com/agntcy/dir); submitted as an individual IETF Internet-Draft (draft-mp-agntcy-ads) |
| Agent Discovery Protocol (ADP) v1.1 | Discover | Protocol | "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]. | Individual IETF submission (RFC stream: None) |
| Agent Identity & Discovery (AID) | Discover | Protocol | "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] | Agent Community as an open-source project; the specification lists "Date: 2 October 2026 Editor: Agent Community Status: Current normative specification" [1]. On naming: "Label governance is separate from the v2 key-format and endpoint-proof updates, and may be addressed by a future working group or BoF process." [1]. No standards body has adopted AID: the IETF drafts are individual submissions, and the Datatracker says "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process" [16]. The _agent label is not in IANA's Underscored and Globally Scoped DNS Node Names registry (checked 2026-10-28) [19]. Licence: the LICENSE file says "This project is dual-licensed under the MIT License and the Apache License 2.0. You may choose either license at your option." [8]; the README says "This project is licensed under the MIT License" [7], and GitHub detects no licence [3] |
| Agent Registration and Discovery Protocol | Discover | Protocol | Expired Internet-Draft (expired 2026-08-28) | IETF individual Internet-Draft |
| Agentic Resource Discovery (ARD) | Discover | Protocol | "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] | The ards-project on GitHub (Apache-2.0) [2][11], with an Oversight Board (seats held by Google, Hugging Face, Microsoft, Amazon and Cisco) and a group of Maintainers chaired by R.V. Guha; spec changes need a majority vote of the Maintainers [9]. No standards body. ARD is not an IETF Internet-Draft; the GitHub repository is its canonical home [2] |
| Agentic Resource Discovery (ARD) manifest | Discover | Term | ||
| Agentmap directive | Discover | Term | ||
| agents.txt | Discover | Protocol | "Status Draft This document is a work in progress and subject to change." [1] | Its maintainers on GitHub: "The agents.txt working group on GitHub." "Structural changes (new directives, schema fields, conformance shifts) require an RFC-style description in the pull request and two reviewer approvals." [2]. Not a standards body |
| AI Catalog well-known file | Discover | Protocol | 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] | Agent Card Working Group Technical Steering Committee (Junjie Bu, Google; Darrel Miller, Microsoft; David Soria Parra, Anthropic; Tadas Antanavicius, PulseMCP) in a Linux Foundation-maintained repository (Apache-2.0 for code, CC-BY-4.0 for specification/docs; SDKs maintained by Luca Muscariello, Cisco, and Jeffrey Damick, AWS) [3][4][5][6] |
| API Catalog (RFC 9727) | Discover | Term | ||
| api-catalog (RFC 9727) | Discover | Protocol | Proposed Standard [2]. One technical erratum (ID 9009, about the Section 5.1 nesting example) reported 2026-06-21, status "Reported" (not verified) [6] | IETF (IETF stream, HTTPAPI working group) [1][2]. Change controller for the well-known URI: IETF [7] |
| Discovery of Model Context Protocol Servers via DNS TXT Records | Discover | Protocol | Active Internet-Draft (-09, Informational; expires 2027-04-25) | Individual Internet-Draft by a single author; not adopted by an IETF working group per the page text (Network Working Group, Intended Status: Informational). |
| DNS-AID (DNS for AI Discovery) | Discover | Protocol | 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") | Individual IETF Internet-Draft with no working-group stream: "Stream state (No stream defined)" [1]; "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process." [1] The open-source project is hosted by the Linux Foundation: "Copyright © DNS-AID a Series of LF Projects, LLC" [2] |
| DNS-Based Agent Naming | Discover | Protocol | Active Internet-Draft (individual, -00), Intended status: Standards Track; IESG state 'I-D Exists'; expires 7 December 2026 | IETF individual Internet-Draft (not adopted by a working group; Datatracker lists no RFC stream). 'dawn' in the draft filename matches the acronym of the IETF DAWN (Discovery of Agents With Names) working group, but this is not a DAWN working-group document |
| Eclipse LMOS (Language Model Operating System) | Discover | Protocol | 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] | Eclipse Foundation, as an Eclipse Technology project. "State Incubating" [7]. Reviews: "Creation Review 2024-12-04"; "2026.09 Progress Review 2026-09-23" [8]. "Project Leads Arun joseph Jasbir Singh amant kumar Patrick Whelan Kai Kreuzer" [9]. Robert Winkler, who presented LMOS to W3C groups [22], is listed under "Historical Committers Robert Winkler" [9] |
| ERC-8444: Agentic Resource Discovery (ARD) Onchain | Discover | Protocol | Draft Standards Track ERC, created 2026-10-12 | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Draft |
| MCP Registry | Discover | Term | ||
| MCP Server Card | Discover | Term | ||
| MCP Server Cards | Discover | Protocol | 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] | Model Context Protocol project, through its Server Card Working Group (chartered 2026-03-26) and the SEP process [1][9] |
| Official MCP Registry | Discover | Protocol | 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 | MCP Registry Working Group, which owns the service, the server.json schema, the Registry API specification and the sub-registry ecosystem [2]. Chartered 2026-04-08; Radoslav Dimitrov (Stacklok) has been sole Lead since 2026-07-30; additive spec changes need Core Maintainer approval [2]. The MCP project sits in the Agentic AI Foundation (AAIF), a directed fund under the Linux Foundation, since 2025-12-09 [15][16] |
| Open Agentic Schema Framework | Discover | Protocol | Active, versioned schema framework | AGNTCY project, published under Linux Foundation-adjacent open governance; source and issue tracker on GitHub, browsable schema at schema.oasf.outshift.com |
| The 'knowledge-linkset' Well-Known URI for Publishing Knowledge Artefacts | Discover | Protocol | Internet-Draft, Intended Status: Informational; expires 17 April 2027; work in progress | Individual Internet-Draft, not adopted by a working group; Informational intended status; the artefact formats are defined in a separate AgenticSystemCore Specification. |
| Well-known URI | Discover | Term | ||
| ACP (four protocols) | General terms | Term | ||
| Agentic web | General terms | Term | ||
| AI agent | General terms | Term | ||
| Agent Identity Protocol (AIP) | Identify | Protocol | Internet-Draft, Intended Status: Standards Track (author's stated intent; not adopted by any WG) | IETF individual draft; sole author, no working group |
| Agent Name Service v2 (ANS) | Identify | Protocol | 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] | No standards body has adopted it. Datatracker: "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process." [1]; API record "stream": null [2]. The Linux Foundation announced on 2026-06-23 "the intent to launch" ANS: "SAN FRANCISCO, June 23, 2026 – The Linux Foundation, the nonprofit organization enabling mass innovation through open source, today announced the intent to launch the Agent Name Service (ANS), a new open standard designed to provide trusted identity, verification, and discovery for AI agents operating across the internet." [21]. GoDaddy says its registry is "Built on the Linux Foundation ANS v2 open standard" [23]. Code lives at github.com/agentnameservice (organization created 2026-05-08 UTC) [13] |
| AI Agent Authentication and Authorization | Identify | Protocol | 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/) | IETF WIMSE working group, which adopted the work on 2026-09-09: "IETF WG state changed to Adopted by a WG" [3][8]. The working group lists "Chairs Justin Richer, Pieter Kasselman" [10]; Kasselman stepped back for this document: "As Pieter is co-author of this document, he has recused himself as chair of any process regarding this work should it continue in the working group, starting with this call for adoption." [7] |
| AI Identity Management System (AIMS) | Identify | Protocol | 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] | IETF WIMSE working group. "Chairs Justin Richer, Pieter Kasselman" [11]. Because Kasselman is a co-author, Richer chairs this document alone: "As Pieter is co-author of this document, he has recused himself as chair of any process regarding this work should it continue in the working group, starting with this call for adoption." [9] |
| Anonymous Bot Authentication | Identify | Protocol | Active Internet-Draft, Intended Status: Informational; expires 20 January 2027; the draft says it 'has not yet seen significant security analysis' | Individual Internet-Draft, not adopted by a working group; source at github.com/ekr/draft-rescorla-anonymous-webbotauth |
| ERC-8004: Trustless Agents | Identify | Protocol | `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] | Ethereum EIP process; no formal steward until finalized |
| ERC-8126: AI Agent Verification | Identify | Protocol | Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| HTTP Message Signatures | Identify | Protocol | 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] | IETF; produced by the httpbis working group, responsible area director Paul Wouters [3]. IANA keeps its registries (signature algorithms, metadata parameters, derived component names, component parameters), with Justin Richer and Manu Sporny as designated experts [6]. The Signature, Signature-Input and Accept-Signature header fields are permanently registered [7] |
| HTTP Message Signatures | Identify | Term | ||
| ID MANDAT: A Machine-Readable Credential for the Agents of a Company | Identify | Protocol | Internet-Draft, Intended Status: Informational; individual submission describing a deployed beta (version 0.3), not the product of an IETF working group | Individual Internet-Draft, not an IETF working group product; the reference registry is operated at idmandat.com |
| JAFAR: A JSON-Based Format for Publishing IP Ranges of Automated HTTP Clients | Identify | Protocol | Active Internet-Draft (draft-illyes-webbotauth-jafar-01), Intended Status: Informational; expires 2027-04-25 | Individual Internet-Draft, not adopted by a working group; despite 'webbotauth' in its name, discussion takes place on the AI Preferences (aipref) Working Group mailing list; source at github.com/garyillyes/jafar |
| Know Your Agent | Identify | Term | ||
| KYA-OS (Know Your Agent Operating System) | Identify | Protocol | 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] | Decentralized Identity Foundation (DIF), KYA-OS Task Force of the Trusted AI Agents Working Group (TAAWG). "The framework is being developed under open, community-driven governance through the KYA-OS Task Force within DIF's Trusted AI Agents Working Group." [11] "You must be a DIF member to participate in this group" [12]. Editor and only listed maintainer is Dylan Hobbs of Vouched: "Editors: Dylan Hobbs" [1]; role `Initial Maintainer, Editor` [4] |
| LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers | Identify | Protocol | 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. | W3C Linked Web Storage Working Group, Recommendation track, under the W3C Patent Policy and the 18 August 2025 W3C Process Document |
| Personal Agent Protocol | Identify | Protocol | 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] | Sierra and Meta with listed design partners; no standards body was found. "These companies will participate in the design process for the draft Personal Agent Protocol, contributing valuable feedback from their unique business perspectives." [13]. "Partners that have agreed to be listed, in alphabetical order." The list names three personal agents (Instinct, Meta, OpenAI), twenty-one companies and nineteen technology providers including Sierra [6]. "Give feedback by opening an issue on GitHub." [6] |
| Security Principal and Verifier Binding for Agent Communication Protocols | Identify | Protocol | Internet-Draft, Intended Status: Informational; expires 17 April 2027 | Individual Internet-Draft submitted under BCP 78 and BCP 79; the draft header carries the label 'Agent Communication Protocols', but Datatracker lists it as an individual draft, not a working-group document. |
| Signature Agent Card (Web Bot Auth registry) | Identify | Protocol | Active Internet-Draft (`draft-meunier-webbotauth-registry-04`, published 27 October 2026, 26 pages, expires 30 April 2027) [1][2][3][4] | Individual IETF Internet-Draft discussed on the IETF **Web Bot Auth (`webbotauth`)** Working Group mailing list (`web-bot-auth@ietf.org`) and presented at IETF 124 (4 November 2025) [1][10][11][12]; not yet adopted as a Working Group document as of 29 October 2026 (`group: "Individual Submissions"`, `iesg_state: "I-D Exists"`) [2][3][11] |
| Signed agent | Identify | Term | ||
| SPIFFE (Secure Production Identity Framework for Everyone) | Identify | Protocol | 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] | The SPIFFE Steering Committee (SSC): "The SPIFFE Project is governed by the SSC that is exclusively responsible for SPIFFE's standards and the Project's strategic goals and direction." "The SSC is comprised of at least five (5) members." [8][9]. A CNCF graduated project [2][23]. Licence: "All software is licensed under the Apache License version 2.0, and all documentation is licensed under the Creative Commons License version 4.0." [8] |
| The Agent Identity Document: A Hosted, Accountable Public Record for AI Agents | Identify | Protocol | Internet-Draft, Intended Status: Informational; expires 13 April 2027 | Individual Internet-Draft by F. Alla; not adopted by an IETF working group. Intended status Informational. |
| Trusted Agent Protocol (TAP) | Identify | Protocol | 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] | Visa alone, under its own terms: "By accessing, downloading, or using this specification, you agree to the terms and conditions outlined in the Visa Trusted Agent Protocol Product Terms." [1]; the sample code is under the Visa Developer Center Terms of Use: "By using, downloading, or installing this code, you agree to the terms and conditions contained in the Visa Developer Center Terms of Use" [10]. It is not the work of a standards body; Visa states only an intent: "We are committed to aligning closely with global standards bodies like IETF, OpenID Foundation and EMVCo." [12] |
| Web Bot Auth | Identify | Protocol | See IETF tracker. | IETF Web Bot Auth (webbotauth) working group, Web and Internet Transport area; chairs David Schinazi and Rifaat Shekh-Yusef, area director Mike Bishop [2]. Charter approved 2025-10-23 [1][3]. Its milestones for sending documents to the IESG are dated 2026-04-30 and 2026-08-31 [2] |
| Web Bot Auth | Identify | Term | ||
| Workload identity | Identify | Term | ||
| Workload Identity in Multi System Environments (WIMSE) | Identify | Protocol | 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] | IETF wimse working group: "Acronym wimse Area Applications and Real-Time Area (art) State Active Charter charter-ietf-wimse-01 Approved" "Chairs Justin Richer, Pieter Kasselman Area Director Charles Eckel" [1]. The charter commits the group to work with "The Cloud Native Computing Foundation (CNCF), particularly with regard to the SPIFFE/SPIRE project." [1]. Naming: the Datatracker group name is "Workload Identity in Multi System Environments", while the charter text says "The Workload Identity in Multi-Service Environments (WIMSE) working group is chartered to address the challenges associated with implementing fine-grained, least privilege access control for workloads deployed across multiple service platforms, spanning both public and private clouds." [1] |
| Workload Identity Metadata | Identify | Protocol | Internet-Draft, Intended Status: Standards Track; expires 19 April 2027 | IETF WIMSE working group mailing list; individual Internet-Draft |
| x401: HTTP Proof Requirement Protocol | Identify | Protocol | 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] | No standards body. Proof runs the repository (proof/x401, Apache-2.0) and site (x401.id). Editors: Daniel Buchner (Proof) and Bhushit Agarwal (Circle). Spec lists named reviewers from Lightspark, MATTR, Okta, OpenAI, Proof, and Visa (listing a reviewer is not a company endorsement) [1][4][7] |
| Agent Commerce Kit (ACK) | Pay | Protocol | 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]. | Catena Labs, with no standards body found. "Catena Labs has contributed ACK as an open-source project" [1]; "The protocols and reference implementations are available under the MIT License." [1] "Copyright (c) 2025 Catena Labs, Inc. and contributors" [4] Catena now calls ACK "Agent Commerce Kit (ACK) - Patterns for standards-based agentic identity and payments curated by Catena." [5] |
| Agent Payments Protocol (AP2) | Pay | Protocol | 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] | FIDO Alliance, since Google donated AP2 on 2026-04-28 [2][3]. Google: "Transitioning ownership to the FIDO Alliance ensures AP2 remains platform-agnostic and community-led, while accelerating adoption of secure agentic payments." [2]. FIDO develops it in its Payments Technical Working Group, chaired by members from Mastercard and Visa, and Google says the work also continues in FIDO's Agentic Authentication Technical Working Group [3][10]. Google's GitHub repository still hosts the specification, documentation and SDK [10] |
| Agent-Initiated Payment Gating | Pay | Protocol | Internet-Draft, Intended Status: Informational; expires 11 April 2027 | Individual IETF Internet-Draft submission, not adopted by a working group |
| Agentic Commerce Protocol | Pay | Protocol | 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] | A Technical Steering Committee (TSC) of up to 7 seats, one per organisation, appointed by the Founding Maintainers, OpenAI and Stripe, who keep a veto "as a last resort" [7]. Seats held on 2026-10-28: OpenAI, Stripe and Meta [7][6]; the commit adding Meta is dated 2026-04-24 [8]. The governance document was first added on 2025-12-02 and replaced by a revised model on 2026-03-10 [8]. Apache-2.0 licence [4]; contributors must sign a CLA [5] |
| Agentic Mobile Protocol (AMP) | Pay | Protocol | 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] | Ant International alone; no standards body or outside editors were found. Licence `"spdx_id": "Apache-2.0"` [7]. Alipay+ "serves as the core payment network infrastructure under this protocol." [1]. Separately, on agent identity: "Ant International, Mastercard, and Visa have begun collaboration on a Know-Your-Agent (KYA) interoperability framework"; "Ant International, Mastercard and Visa will collaborate through BuildFin.ai to advance common approaches for AI agent verification, accountability and risk management across payment ecosystems in Singapore." [11] |
| Agora (agent marketplace protocol) | Pay | Protocol | Testnet-only; production_status explicitly "testnet-only" in its own manifest | Single vendor / independent project (agoraproto.org) |
| AP2 Checkout Mandate | Pay | Protocol | AP2 specification component, not an independently published protocol | FIDO Alliance / AP2 (see ap2 record) |
| Buyer of Record & Merchant of Record (Agentic Commerce) | Pay | Term | ||
| Cloudflare Pay Per Crawl | Pay | Protocol | Closed beta (as of 2026-07-28), launched as a private beta on 2025-07-01 | Cloudflare (single vendor) |
| EMV® Agentic Payments – Framework for Specifications | Pay | Protocol | 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 | EMVCo. "EMVCo is collectively owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa." [7]. "EMVCo is managed by the Board of Managers, which is comprised of two representatives from each of the member organisations." "Matt Crothers currently serves as Chair of the EMVCo Board of Managers, representing American Express." [8]. Neither page names Capital One [7][8]. Associates review drafts first: "Following initial review from EMVCo Associates, EMV ® Agentic Payments – Framework for Specifications is now available for public review until Wednesday 30 September." [2]. Release of a final draft work item goes to an Advisor vote: "A simple majority of the non-abstaining voting Advisors must vote in the affirmative for a final draft Work Item to be released." [9] |
| ERC-8183: Agentic Commerce | Pay | Protocol | Draft ERC — 'This specification defines the Agentic Commerce Protocol: a job with escrowed budget...' | Ethereum EIP/ERC process (Ethereum Magicians discussion + EIPs repository); status Draft, an ERC Standards Track proposal, not yet Final |
| Facilitator | Pay | Term | ||
| HTTP 402 Payment Required | Pay | Term | ||
| Human Not Present | Pay | Term | ||
| KYAPay Token | Pay | Protocol | 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] | No standards body. It is an individual Internet-Draft by Ankit Agarwal (Skyfire) and Michael B. Jones (Self-Issued Consulting): "Document Type Active Internet-Draft (individual)" "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process." [2]. It is discussed on the OAuth working-group list, but the working group has not adopted it [11][2]. The draft expects that: "Note that, in the future, the payment token functionality could be split into a separate specification, if desired by a working group adopting the specification." [1] |
| L402 | Pay | Protocol | 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] | Lightning Labs (single vendor). The text lives in the lightninglabs/L402 repository on GitHub [1]; on 2026-03-11 (UTC) Osuntokun wrote of that repository: "We plan on continuing development of the protocol there." [8]. It was also submitted to the Lightning bLIP repository as PR #26, opened 2023-06-07 (UTC) and still open and unmerged on 2026-10-29 [6]. GitHub lists no licence for the L402 repository [3]; the bLIP text is CC0 [7] |
| Machine Payments Protocol (MPP) | Pay | Protocol | "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) | Tempo and Stripe, in the open tempoxyz/mpp-specs repository: "MPP is developed in the open on GitHub." [2]. mpp.dev splits governance in two. Core: "The core specification is published as the Payment HTTP Authentication Scheme and submitted to the IETF standards track, where it continues to progress as an open, vendor-neutral standard." [2]. Payment methods: "Each payment method specification is defined and maintained by the rail behind it—for example Visa, Mastercard, Solana, Bitcoin, Stripe, or Tempo—together with any corporate entities associated with that rail." "Payment rails and third parties do not need explicit approval to add a payment method implementation to MPP." [2]. The IETF has not adopted the draft: "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process." [8]. There is no MPP foundation or IETF working group |
| Mandate | Pay | Term | ||
| Pay per crawl | Pay | Term | ||
| s402 | Pay | Protocol | Archived repository (observed 2026-10-16) | Single open-source project (s402-protocol on GitHub); no standards body, no foundation; explicitly a 'profile' of x402 rather than a competing standards effort |
| Universal Commerce Protocol (UCP) | Pay | Protocol | 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] | A Governing Council (GC) of five seats: one permanent seat each for the founding organisations, Google and Shopify, and three elected seats [7]. On 2026-10-28 the seats were held by Google, Shopify and Stripe, with two open [8]; Stripe joined on 2026-04-28 [9]. GOVERNANCE.md says "GC serves as the ultimate owner of all UCP assets. Google acts as the custodian of the UCP.dev domain, holding and managing it to foster adoption of UCP." and "Google holds proxy vote for all open seats until Dec 2028 to facilitate rapid early stage growth & adoption of the protocol." [7]. Four Domain Tech Councils write the specification: Shopping, Food (formed 2026-07-16; initial members Block (Square), DoorDash, Google, Toast and Uber Eats), Lodging (formed 2026-08-11; inaugural members Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com) and Payments (formed 2026-09-02; inaugural members Adyen NV, Ant International, Coinbase, Global Payments, Google, PayPal, Shopify and Stripe); of the GC, GOVERNANCE.md says "May choose to review and veto a DTC decision or recommendation." [7][9]. Apache-2.0 licence [5][6]; contributors sign a CLA [7] |
| VCAP: Verified Commerce for Agent Protocols | Pay | Protocol | Active Internet-Draft (individual); Intended status: Informational (draft header; Datatracker stream status is None) | IETF individual Internet-Draft; not endorsed by the IETF, no working group, no formal standing in the IETF standards process |
| x402 | Pay | Protocol | In production use; the Foundation calls it "an open, neutral standard for internet-native payments" [6] | The x402 Foundation, a Linux Foundation project ("x402 a Series of LF Projects, LLC") [6]. The Linux Foundation announced it on 2026-04-02 with the contribution of the protocol from Coinbase [3], and announced its operational launch and the completed contribution on 2026-07-14, with 40 member organisations by then [4]. Premier members (2026-07-14): Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe and Visa [4]. Michael Hursta was appointed Executive Director on 2026-10-01 [5]. The Technical Steering Committee lists Coinbase, Cloudflare and Stripe [7] |
| x402 Payment Payload | Pay | Term | ||
| AAuth (Hardt) | Permit | Protocol | Active Internet-Draft (individual), expires 2027-03-29 UTC: "expires": "2027-03-29T16:59:56Z" [2] | The author, as an individual Internet-Draft; no IETF working group has adopted it. "Document Type Active Internet-Draft (individual) Author Dick Hardt Last updated 2026-09-25 Replaces draft-hardt-aauth-protocol" "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process" [1]. The OAuth WG heard it at an interim on 2026-10-05, where the open question was "Where should this work happen?": "Option A In the OAuth WG" or "Option B In a new WG" [17][18] |
| AAuth Rich Resource Requests | Permit | Protocol | Exploratory Draft (-00); no known implementations | Individual IETF Internet-Draft submission, companion to the AAuth Protocol; no working group. |
| Agent Authorization Envelope | Permit | Protocol | Active Internet-Draft (-02, expires 2027-03-10) | Individual Internet-Draft submitted to the IETF datatracker by a single author; not adopted by a working group per the page. |
| Agent Authorization Grant | Permit | Protocol | Expired Internet-Draft (expired 2026-04-23) | IETF individual Internet-Draft (OAuth-adjacent, not yet adopted by the OAuth Working Group as of this verification) |
| Agent Authorization Profile | Permit | Protocol | Expired Internet-Draft (expired 2026-08-11) | No formal governance body; single individual author plus a GitHub organization (aapspec) hosting the spec text, reference implementation, schemas, and test vectors |
| Agent Context Interchange Protocol | Permit | Protocol | Internet-Draft, Intended Status: Informational; expires 15 April 2027; work in progress | Individual Internet-Draft, Network Working Group; not adopted by an IETF working group |
| Agent Delegation Receipts | Permit | Protocol | Internet-Draft (draft-nelson-agent-delegation-receipts-15), Intended Status: Informational; expires 2027-04-25 | Individual Internet-Draft submitted to the IETF (Network Working Group); not an adopted working group document. |
| Agent Identity Protocol (AIP): Verifiable Delegation for AI Agent Systems | Permit | Protocol | Internet-Draft, Intended Status: Standards Track; expires 13 April 2027 | Individual Internet-Draft by a single independent author; Intended Status: Standards Track |
| agent-permissions.json | Permit | Protocol | 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] | Lightweight Agent Standards Working Group (LAS-WG), chaired by Samuele Marro (University of Oxford and Institute for Decentralized AI), governed by the LAS-WG Charter (11 voting member organizations, one-organization-one-vote backstop, CC BY 4.0 outputs) [5][8][11][14][15][16] |
| Agentic Authority Graph Validation | Permit | Protocol | Internet-Draft, Intended Status: Experimental; expires 17 April 2027 | Individual Internet-Draft submission (no working group), author D. O. Watts |
| AI crawler tokens | Permit | Term | ||
| AI crawler tokens in robots.txt | Permit | Protocol | In production: 11 vendors' tokens documented on pages fetched today, and named by 32 of the 36 sites probed | Each vendor's own documentation; the IETF governs only the underlying robots.txt syntax (RFC 9309) |
| ai.txt | Permit | Protocol | 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] | None across the filename. Spawning Inc. maintains the 2023 `/ai.txt` generator and WordPress plugin [1][2]; Kayla Cardillo maintains `draft-car-ai-txt-wellknown-00` and `kaylacar/ai-txt` as an independent submission [5][6] |
| AIPREF Content-Usage Attachment | Permit | Protocol | 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] | IETF AI Preferences (aipref) working group: "Chairs Mark Nottingham, Suresh Krishnan Area Director Mike Bishop" [7]. The charter asks for "Standard track document(s) describing means of attaching or associating those preferences with content in IETF-defined protocols and formats, including but not limited to using Well-Known URIs (RFC 8615) such as the Robots Exclusion Protocol (RFC 9309), and HTTP response header fields" [7]. Discussion is on the ai-control@ietf.org list and the source is in the GitHub repository ietf-wg-aipref/drafts [1] |
| AIPREF Vocabulary (A Vocabulary For Expressing AI Usage Preferences) | Permit | Protocol | 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] | IETF AI Preferences (aipref) working group: "Area Web and Internet Transport (wit) State Active Charter charter-ietf-aipref-01 Approved" "Chairs Mark Nottingham, Suresh Krishnan Area Director Mike Bishop" [7]. The group was created on 2024-11-19 and its charter approved on 2025-01-07: "2025-01-07 Cindy Morgan Charter approved, group active" [8]. Work happens on the ai-control@ietf.org list and in the GitHub repository ietf-wg-aipref/drafts [7][22] |
| An Attenuated Delegation Profile for Automated Agents | Permit | Protocol | "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]. | Individual IETF Internet-Draft (replaces draft-hassan-oauth-agent-delegation); not a working-group document. |
| auth.md | Permit | Protocol | Reference specification at `v0.6.0` (10 June 2026); generally available in WorkOS AuthKit (`Agent Registration`) since 4 August 2026 [4][5][13][18] | WorkOS (`workos/auth.md`, MIT License); an independent community hub (`auth-md.com`) and generator/validator skill (`fabricioctelles/skills`) are maintained separately by Fabricio Telles [2][6][19][22][23] |
| CoMP (Content Monetization Protocols) | Permit | Protocol | CoMP v1 (Final): open for public comment until 2026-04-09 and finalized 2026-04-28, per IAB Tech Lab's initiative page | IAB Tech Lab; specification under CC-BY 3.0 in github.com/IABTechLab/CoMP |
| Content Signals Policy | Permit | Protocol | 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] | Cloudflare; a policy text it publishes and serves on its network [1][4]. No standards body has adopted it. On launch day Cloudflare told the IETF aipref list: "We see this as an interim measure to address immediate needs, while work is done towards standardization." "We will continue to engage in this working group and hope we can achieve a consensus position and will revisit our policy once that has happened." [7]. Cloudflare's individual Internet-Draft, draft-romm-aipref-contentsignals-00 (2025-10-01), is listed on the IETF Datatracker as "Expired Internet-Draft (individual)", with "Authors Michael Tremante, Leah Romm Last updated 2026-04-04 (Latest revision 2025-10-01)" [8] |
| Content usage preference | Permit | Term | ||
| Content-Signal directive | Permit | Term | ||
| Credential Delegation Protocol for AI Agents in Multi-System Environments | Permit | Protocol | Internet-Draft, Intended Status: Standards Track; expires 16 April 2027 | Individual Internet-Draft submitted to the IETF WIMSE Working Group mailing list; source on GitHub (cred-ninja/protocol) |
| Dynamic Client Registration & Client ID Metadata | Permit | Term | ||
| ERC-8196: AI Agent Authenticated Wallet | Permit | Protocol | Final Standards Track ERC (Final 2026-07-21); requires ERC-4337 and ERC-8126 | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| ERC-8226 Regulated Agent Mandate | Permit | Protocol | Draft, Standards Track: ERC (marked ⚠️ Draft on eips.ethereum.org) | Ethereum ERC process (Ethereum Magicians discussion thread + ethereum/ERCs GitHub repo); not yet adopted by an EIP editor as Final |
| Expired Internet-Draft | Permit | Term | ||
| High-Assurance Agent Control Envelope | Permit | Protocol | Internet-Draft, Intended Status: Informational; expires 18 April 2027 | Individual Internet-Draft by a single author, submitted to the IETF Network Working Group; not adopted by a working group |
| Identity Assertion JWT Authorization Grant (ID-JAG) | Permit | Protocol | 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] | IETF OAuth Working Group (Web Authorization Protocol). WG adoption: the WG -00 was posted "rev": "00", "time": "2025-09-08T21:11:46Z" (UTC; 2025-09-09 00:11 EEST) [4]; "Replaces draft-parecki-oauth-identity-assertion-authz-grant" [1] |
| Identity Continuation Assertion for OAuth 2.0 Token Exchange | Permit | Protocol | "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]. | Individual IETF Internet-Draft (discussion routed to the OAuth Working Group mailing list); not a working-group document. |
| OAuth Client ID Metadata Document | Permit | Protocol | 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 | Active Internet-Draft and Working Group Document of the IETF Web Authorization Protocol (`oauth`) Working Group (`Intended status: Standards Track`; replaces individual draft `draft-parecki-oauth-client-id-metadata-document`) [1][2][3] |
| OAuth Profile for Delegated AI Agent Authorization | Permit | Protocol | Internet-Draft, individual submission, Active | IETF individual Internet-Draft (OAuth-adjacent; not yet adopted by the OAuth Working Group as of this verification) |
| OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) | Permit | Protocol | 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 | IETF OAuth Working Group; both are Internet Standards Track RFCs with IETF/IESG consensus |
| OpenA2A Agent Authorization Protocol | Permit | Protocol | See IETF tracker. | Its author, A. Fane of OpenA2A [1][2]. Datatracker shows "RFC stream (None) Intended RFC status (None)" [2] |
| Per-Call Proof for Local Tool Invocation by AI Agents | Permit | Protocol | Internet-Draft, Intended Status: Standards Track; expires 15 April 2027 | Individual IETF Internet-Draft, not a working-group document (Datatracker: Active Internet-Draft (individual)); the draft directs discussion to the WIMSE Working Group mailing list |
| Protected Resource Metadata | Permit | Term | ||
| Really Simple Licensing | Permit | Protocol | Recommendation (RSL's own maturity label, not a W3C/IETF Recommendation) — Document RSL-SPEC-1.0, Category 'Industry Specification' | RSL Collective, a vendor consortium; issue tracker at github.com/rslstandard/rsl |
| Roots | Permit | Term | ||
| TDMRep (TDM Reservation Protocol) | Permit | Protocol | 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] | The W3C Text and Data Mining Reservation Protocol Community Group, chaired by Laurent Le Meur (EDRLab) and Giulia Marangoni (AIE - Italian Publishers Association) [6]. The spec was "published by the Text and Data Mining Reservation Protocol Community Group under the W3C Community Final Specification Agreement (FSA)." [1] Work continues on GitHub at w3c-cg/tdm-reservation-protocol, last pushed 2026-09-03 UTC [7] |
| Workload Authorization Grant (WAG) | Permit | Protocol | "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] | No working group. Datatracker group: "name": "Individual Submissions" [2]; "This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process." [1]. Presented at the WIMSE working group's interim on 2026-10-07 16:00 UTC (19:00 EEST): "Present and discuss the Workload Authorization Grant draft:" [11]. The follow-up list message says: "*This is not a call for adoption* of the draft or of any particular solution. We only want to know whether this is a problem the working group should spend time on." [14] |
| A2UI (Agent to UI) Protocol | Present | Protocol | 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] | The A2UI open-source project in the a2ui-project GitHub organisation (organisation created 2026-03-03) [4][5]; the old address https://github.com/google/A2UI now answers with an HTTP 301 redirect to https://github.com/a2ui-project/a2ui (checked 2026-10-28). Contributions go through the Google CLA: "Contributions to this project must be accompanied by a Contributor License Agreement (CLA)." and "This project follows Google's Open Source Community Guidelines" [7]. Licence Apache-2.0 [4][8]. No standards body or foundation was found holding A2UI (checked 2026-10-28) |
| Agent-to-Wallet Protocol for Digital Credentials | Present | Protocol | Internet-Draft, Intended Status: Standards Track; expires 20 April 2027; work in progress | Individual Internet-Draft (Datatracker: Active Internet-Draft (individual)); not adopted by a working group. "Network Working Group" is only the draft header label |
| Agent-User Interaction Protocol (AG-UI) | Present | Protocol | 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] | The CopilotKit team. The repository's CODEOWNERS file assigns every path by default to the CopilotKit team (* @ag-ui-protocol/copilotkit) [6], and integration authors can be added as co-owners: "This step is only needed if you want to be added as a co-owner who can merge changes to your integration without core team review." [7]. The README lists a "Biweekly AG-UI Working Group" [3]. No foundation, steering committee or governance document was found in the repository or the documentation |
| Generative UI | Present | Term | ||
| Interrupt | Present | Term | ||
| MCP Apps | Present | Protocol | 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] | Model Context Protocol project, through the SEP process for official extensions (Extensions Track) [1][12]. The spec and SDK live in the modelcontextprotocol/ext-apps repository [4] |
| Agent Readability Spec | Read | Protocol | 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] | Original checklist (March 2026): Timothy Jordan at Vercel (subsequently maintained as `a14y` at `https://a14y.dev/spec/`) [3][6][7]; empirical guide & open standard (August–October 2026): Vercel and the Ora research lab (`ora.ai`) at `agentready-org/standard` (`https://www.agentready.org/`) [1][11][12][15] |
| AGENTS.md | Read | Protocol | Open format stewarded by the AAIF; not standards-track | Agentic AI Foundation (AAIF), under the Linux Foundation |
| Apache Ossie (formerly Open Semantic Interchange) | Read | Protocol | 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] | Apache Software Foundation, Apache Incubator. "Apache Ossie is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC." [11]. Vote opened 2026-06-16: "I call for a formal vote to accept Ossie into the Apache Incubator." [15]; result: "This vote passed with the following result:" ([RESULT][VOTE] Accept Ossie into the Apache Incubator 2026/06/19 06:03:11 UTC) [16]. "Started: 2026-06-19"; "Committers: 17 PPMC members: 7" [13]. "Champion jbonofre JB Onofre Mentors jbonofre JB Onofré. holden Holden Karau. tison Zili Chen. russellspitzer Russell Spitzer" [12] |
| Coding agent instruction files | Read | Term | ||
| Context compaction | Read | Term | ||
| llms.txt | Read | Protocol | Community proposal (v2), not standards-track | Jeremy Howard (via the AnswerDotAI/llms-txt GitHub repo) |
| llms.txt | Read | Term | ||
| Markdown for Agents | Read | Protocol | Beta; free on Pro, Business and Enterprise plans and for SSL for SaaS customers [1][2] | Cloudflare; a feature of its network, documented in Cloudflare's developer docs [1] |
| Markdown twin | Read | Term | ||
| MCP Resource | Read | Term | ||
| Open Knowledge Format | Read | Protocol | Pre-1.0. Google called v0.1 "a starting point, not a finished standard" [5]. Repository licensed Apache-2.0 [2] | Google Cloud, in the GoogleCloudPlatform/open-knowledge-format GitHub repository, created 2026-08-11 [2]. The first copy, under okf/ in GoogleCloudPlatform/knowledge-catalog, is now a frozen snapshot [3] |