All articles
92 articles across nine categories, plus general terms. Every cell has a source or says it does not. JSON · CSV · how rows get here
| 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 | IETF individual Internet-Draft; not adopted by any IETF working group, 'not endorsed by the IETF' and has 'no formal standing' in the IETF process (datatracker's own disclaimer) |
| Verifiable Intent | Account | Protocol | Draft (v0.1); open-sourced specification and reference implementation | Maintained by Mastercard; open to multi-stakeholder contribution per the project's CONTRIBUTING.md; built on FIDO Alliance, EMVCo, IETF and W3C primitives (SD-JWT/RFC 9901, key confirmation/RFC 7800) |
| Ad Context Protocol | Act | Protocol | Active open protocol, documented current release 3.1.20 | AgenticAdvertising.org, an industry organization of publishers, platforms, agencies, and technology providers; foundation governance (structure, voting classes, Board composition, spec lifecycle) is set out in the project's CHARTER.md and published at agenticadvertising.org/governance |
| Agent Client Protocol | Act | Protocol | v1 stable and shipping; v2 published in Draft form as of 2026-07-20 | Zed Industries acts as BDFL/design-team lead over a public Request for Dialog (RFD) process; Sergey Ignatov (JetBrains) joined as a second Lead Maintainer on 2026-02-18, reflecting growing Zed/JetBrains collaboration |
| Agent Connect Protocol (AGNTCY) | Act | Protocol | OpenAPI 3.1.1 specification, version 0.2.3; source repository archived (read-only) by the owner on 2026-04-11; the rendered interactive spec at spec.acp.agntcy.org still resolves and is unchanged since its last update in May 2025 | AGNTCY project (Cisco donated AGNTCY to the Linux Foundation); the acp-spec GitHub repository was archived by its owner (the agntcy GitHub organization) on 2026-04-11 and is now read-only, while the broader AGNTCY project (49 repositories, most recently updated within hours of this check) remains active under Linux Foundation governance, with its discovery/identity work now centered on the 'dir' (Distributed Announce and Discovery) and OASF (Open Agentic Schema Framework) projects rather than acp-spec |
| Agent Protocol | Act | Protocol | "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 Skills | Act | Protocol | Active open format, described on agentskills.io as adopted by a growing number of agent products | Originally developed and released as an open format by Anthropic; now described by its own site as "open to contributions from the broader ecosystem" with development happening in the community-run github.com/agentskills/agentskills org and a public Discord |
| 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 | "An open specification", version 0.1.0 as published by Wildcard | Wildcard AI; single company controls the spec and the reference "Wildcard Bridge" runtime and maintains a discretionary registry of published files |
| Model Context Protocol | Act | Protocol | Active open specification, current dated release 2026-07-28 | Agentic AI Foundation (Linux Foundation umbrella); day-to-day spec work in the modelcontextprotocol GitHub org via public SEPs (Specification Enhancement Proposals) and working groups |
| NLWeb | Act | Protocol | "Main reference implementation... implemented in Python"; described by its own README as a proof-of-concept the community is invited to build alternative implementations of, not a definitive solution | Originated at Microsoft; the reference implementation now lives under a separate community GitHub org (nlweb-ai), not microsoft/NLWeb directly — github.com/microsoft/NLWeb redirects to github.com/nlweb-ai/NLWeb |
| OpenAI Plugins (formerly Apps SDK) | Act | Protocol | Active vendor product, rebranded from "Apps SDK" to "Plugins" as the top-level developers.openai.com section name (developers.openai.com/apps-sdk now redirects to developers.openai.com/plugins) | OpenAI, unilaterally, for the ChatGPT-specific extension layer (window.openai bridge, submission/review process); the underlying UI transport (MCP Apps) is co-governed via the modelcontextprotocol org, and OpenAI's documentation explicitly directs developers to prefer the shared MCP Apps standard over ChatGPT-specific extensions wherever it covers the need |
| Origin trial | Act | Term | ||
| Web Agent Protocol (WAP) | Act | Protocol | "A standardized framework designed to enable seamless interaction between users, web agents, and browsers by recording and replaying browser actions" (repository's own description) | 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, dated 4 September 2026; explicitly "not a W3C Standard nor on the W3C Standards Track" | W3C Web Machine Learning Community Group; editors are Brandon Walderman (Microsoft), Khushal Sagar (Google), Dominic Farolino (Google) |
| 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 Network Protocol | Coordinate | Protocol | Released v1.1 (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 |
| Agent2Agent Protocol | Coordinate | Protocol | Stable, v1.0.0 | Linux Foundation (A2A Project); contributed by Google |
| 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 | Research protocol with reference implementation and demo | Academic research project (Oxford / Camel AI); community-maintained code |
| AITP (Agent Interaction & Transaction Protocol) | Coordinate | Protocol | Version: 0.1.0. Status: Draft. "AITP is a spec in progress and we are open to comments, feedback, and contributions" (project's own words) | NEAR AI-led open-source specification, MIT licensed (github.com/nearai/aitp); developed in parallel with NEAR AI's own agent hub and community input via Telegram/GitHub issues and PRs; no independent standards body |
| 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' as of this check (docs moved from docs.coralprotocol.org to docs.coralos.ai); not a multi-stakeholder standards body |
| Natural Language Interaction Protocol | Coordinate | Protocol | Ecma International Standard, 1st edition, published 10 December 2025 (ECMA-430 core spec, plus companion ECMA-431/432/433 transport bindings, ECMA-434 security profiles, and ECMA TR/113 explanatory report); an ISO standardisation ballot was reported in progress by project contributors as of August 2026 | Ecma International Technical Committee TC56 (NLIP), with an ISO ballot in progress as of mid-2026 per contributor reports; incubated and supported by the Enterprise Neurosystem community |
| Secure Low-Latency Interactive Messaging | Coordinate | Protocol | "Next-generation communication framework that provides the secure, scalable transport layer for AI agent protocols like A2A and MCP" | Linux Foundation (AGNTCY project); originally donated by Cisco |
| 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 | Discover | Protocol | Internet-Draft; work in progress | IETF individual Internet-Draft; explicitly delegates its DNS layer to the separate dnsop-area DNS-AID draft rather than defining its own |
| Agent Identity and Discovery | Discover | Protocol | Current normative specification | Agent Community open-source project; editor listed as 'Agent Community'; no formal standards body, though the spec discusses composing with IETF-track work (RFC 9421, RFC 7638, RFC 9728, RFC 8414) |
| Agent Registration and Discovery Protocol | Discover | Protocol | Internet-Draft; work in progress | IETF individual Internet-Draft |
| Agentic Resource Discovery | Discover | Protocol | Proposal | Authored by individuals at Google, Microsoft and Hugging Face (Junjie Bu, R.V. Guha, Shaun Smith); published as an open GitHub project (ards-project/ard-spec) with no formal standards body yet; contributions acknowledged from AWS, Cisco, Databricks, GitHub, GoDaddy, Nvidia, Salesforce and Snowflake |
| Agentmap directive | Discover | Term | ||
| agents.txt | Discover | Protocol | "An open standard proposal for declaring what AI agents can do on a website" (kaylacar/agents-txt); a Mastercard developer-documentation page independently characterizes the space as "IETF draft expired ... fragmented landscape with 11+ competing proposals ... no ratified standard" | None; at least three non-converging proposals (agents-txt.com, kaylacar/agents-txt, agentstxt.dev) each self-describe as "the" agents.txt standard, with no shared maintainer or reconciliation process found |
| AI Catalog well-known file | Discover | Protocol | Deprecated predecessor path of the ARD manifest | ARD / ards-project (see ard) |
| api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs | Discover | Protocol | Proposed Standard (errata exist) | IETF; published as a Standards Track RFC with the IETF as change controller |
| DNS for AI Discovery | Discover | Protocol | Internet-Draft, Standards Track intended status | IETF dnsop working group Internet-Draft (individual submission track, not yet WG-adopted) |
| 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 Independent Submission (individual draft; not sponsored by a chartered working group; 'dawn' in the draft filename is a keyword, not a working-group name) |
| LMOS (Language Model Operating System) | Discover | Protocol | LMOS Protocol spec is explicitly "work in progress and contains empty sections"; "It is not a W3C Standard nor is it on the W3C Standards Track" (project's own words), though the project states it plans to start the formal W3C process once mature | Eclipse Foundation open-source project (Eclipse Public License-compatible governance); code Apache License 2.0; top committer affiliated with Deutsche Telekom (openHAB/Kai Kreuzer lineage); not yet on the W3C standards track |
| MCP Server Card | Discover | Term | ||
| 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 |
| Well-known URI | Discover | Term | ||
| ACP (three protocols) | General terms | Term | ||
| Agentic web | 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 Internet-Draft, Intended Status: Informational | IETF Independent Submission (individual draft; not sponsored by a chartered WG); replaces the authors' earlier draft-narajala-ans |
| AI Agent Authentication and Authorization (AIMS) | Identify | Protocol | Active Internet-Draft (individual submission), Internet-Draft, no RFC stream and no intended RFC status assigned; expires 2027-01-07 | Individual IETF Internet-Draft under consideration by the IETF WIMSE working group (Applications and Real-Time Area); not yet a WG document as of 2026-09-07. Chairs of WIMSE: Justin Richer and Pieter Kasselman (a co-author of this draft, recused from chairing this specific adoption process). |
| ERC-8004: Trustless Agents | Identify | Protocol | Draft Standards Track ERC | Ethereum EIP process; no formal steward until finalized |
| HTTP Message Signatures | Identify | Protocol | Proposed Standard | IETF |
| Signature Agent Card (Web Bot Auth registry) | Identify | Protocol | Active Internet-Draft (individual), Intended Status: Informational | IETF individual draft, discussed on the web-bot-auth@ietf.org list; not yet adopted by the webbotauth WG (unlike the sibling httpsig-protocol draft) |
| SPIFFE (Secure Production Identity Framework for Everyone) | Identify | Protocol | Active, stable open-source specification set (SPIFFE/SPIRE); SPIFFE itself makes no agent-specific claims | CNCF (SPIFFE is a graduated CNCF project); the AI-agent profile is governed separately as an IETF individual draft, not by the SPIFFE project itself |
| Visa Trusted Agent Protocol | Identify | Protocol | Active vendor-led merchant specification | Visa (single-vendor specification, published for merchant/developer adoption) |
| Web Bot Auth HTTP Message Signatures | Identify | Protocol | Active Internet-Draft, WG Document, Intended Status: Informational | IETF webbotauth Working Group (chartered; document adopted as a WG item 2026-09-01) |
| Workload Identity in Multi System Environments (WIMSE) Architecture | Identify | Protocol | Active Internet-Draft, WG Document, Intended Status: Informational | IETF wimse Working Group (chartered WG; RFC stream IETF) |
| Agent Payments Protocol | Pay | Protocol | Security/authorization protocol for agent-performed payments; core spec now stewarded by FIDO Alliance | Core specification donated by Google to the FIDO Alliance for continued development; the google-agentic-commerce/AP2 repository now hosts only samples and an SDK, not the normative spec text |
| Agentic Commerce Protocol | Pay | Protocol | Beta open standard, interaction model for connecting buyers, agents, and businesses | Technical Steering Committee (up to 7 org seats); OpenAI, Stripe, and Meta are lead maintainers, with OpenAI and Stripe as Founding Maintainers holding last-resort veto over mission, neutrality, security, and fork-integrity decisions |
| 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) |
| EMV Agentic Payments – Framework for Specifications | Pay | Protocol | Draft v1.0, released for public review and comment; EMVCo describes it as ‘a foundation for further industry engagement and potential specification development’, not itself a finished specification | EMVCo, the technical body jointly owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa, which creates and manages the EMV Specifications; this framework is being developed by EMVCo's dedicated Agentic Payments Task Force with input from EMVCo Associates and Subscribers, and in collaboration with the FIDO Alliance, the OpenID Foundation, the OpenWallet Foundation and W3C |
| 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 | ||
| L402 | Pay | Protocol | Active, registered as an HTTP Authentication scheme (RFC 7235-style) | Lightning Labs |
| Machine Payments Protocol | Pay | Protocol | Open protocol; developer docs distinguish the normative IETF specification from the mpp.dev developer-friendly overview | Co-authored by Tempo and Stripe; the core specification (the abstract 402/Challenge/Credential/Receipt shape) is submitted to the IETF standards track as the Payment HTTP Authentication Scheme, while individual payment methods (Tempo, EVM, Stripe Card, Lightning, Solana, Stellar, Monad, NEAR Intents, RedotPay) are maintained separately from the core, to keep the core neutral to any one rail |
| Mandate | Pay | Term | ||
| s402 | Pay | Protocol | Draft wire-format specification, actively developed (commits as recent as 2026-09-04) | 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 | Pay | Protocol | Open standard; specification expanding beyond Shopping into Lodging and Food | Domain Tech Councils (DTC) per vertical — Shopping Tech Council and Food Tech Council seated — under an overall Governing Council (GC); DTC seats held by Google, Shopify, Etsy, Meta, Amazon, Microsoft, Target, Stripe, Salesforce, Wayfair, Square, Toast, DoorDash, Uber Eats |
| VCAP: Verified Commerce for Agent Protocols | Pay | Protocol | Active Internet-Draft (individual); Intended RFC status: Informational | IETF individual Internet-Draft; not endorsed by the IETF, no working group, no formal standing in the IETF standards process |
| x402 | Pay | Protocol | Open, neutral standard for internet-native payments | x402 Foundation, a Series of LF Projects, LLC (Linux Foundation); operational launch announced 2026-07-14 |
| Agent Authorization Grant | Permit | Protocol | Internet-Draft, individual submission; page marked "Expired" by the IETF Datatracker | 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 (individual), per the IETF Datatracker; last updated 2026-08-11, latest revision -01 dated 2026-02-07 | No formal governance body; single individual author plus a GitHub organization (aapspec) hosting the spec text, reference implementation, schemas, and test vectors |
| agent-permissions.json | Permit | Protocol | v1.0.0, complete JSON Schema published; described by the working group's own arXiv paper as a proposal, not an adopted standard | Lightweight Agent Standards Working Group (LAS-WG), an open community project hosted on GitHub at las-wg/agent-permissions.json; no formal standards-body affiliation found |
| AI crawler tokens | Permit | Term | ||
| AI Crawler User-Agent Tokens in robots.txt | Permit | Protocol | A convention, not a formal spec; each vendor's documentation is normative only for that vendor's own crawler | No single governing body; each vendor unilaterally defines and documents its own token(s); RFC 9309 (IETF, Standards Track) governs the underlying robots.txt syntax all of them use |
| ai.txt | Permit | Protocol | IETF Internet-Draft (draft-car-ai-txt-wellknown-00) presented as a formal well-known-URI registration proposal; kaylacar/ai-txt separately claims IANA filing (#76/#77, 'under review') | None; at least three independent proposals for the same policy-declaration purpose (an IETF Internet-Draft by 'car', kaylacar/ai-txt, and an arXiv DSL paper) plus a fourth, differently-scoped product (aitxt.ing) all use the same filename with no shared authority |
| AIPREF Content-Usage Attachment | Permit | Protocol | Internet-Draft, work in progress; "About This Document" note says it is to be removed before publishing as an RFC | IETF AI Preferences Working Group (ai-control@ietf.org mailing list) |
| AIPREF Vocabulary | Permit | Protocol | Internet-Draft, work in progress; explicitly states its contents 'DO NOT REFLECT CONSENSUS of the Working Group' | IETF AI Preferences Working Group (ai-control@ietf.org mailing list) |
| auth.md | Permit | Protocol | Published protocol specification at auth-md.com/specification; not submitted to IETF, W3C, or any standards body | Single vendor (auth-md.com, associated with WorkOS and founder Fabricio Telles); adopted by several named third parties (Resend, Cloudflare, Firecrawl, Alpic, here.now, mailbox.bot) who each publish their own auth.md file |
| Content Signals Policy | Permit | Protocol | Vendor-published policy convention layered on robots.txt; not submitted to a standards body as of this verification | Cloudflare, developed with publisher/platform partners named in the announcement (e.g. Condé Nast, News/Media Alliance, Reddit, Pinterest, Quora, Yahoo) |
| 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 |
| Identity Assertion JWT Authorization Grant | Permit | Protocol | Active Internet-Draft, WG Document (oauth WG); Intended status: Standards Track (per document front matter); IESG state: I-D Exists | IETF OAuth (Web Authorization Protocol) Working Group; WG Document as of this verification, individual submission originated 2024-03 |
| 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 | Internet Standard (RFC 8414, published June 2018) and Internet Standard (RFC 9728, published 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 |
| 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 |
| Text and Data Mining Reservation Protocol | Permit | Protocol | W3C Community Group Final Report; explicitly "not a W3C Standard nor is it on the W3C Standards Track" | W3C Text and Data Mining Reservation Protocol Community Group |
| A2UI (Agent to UI) Protocol | Present | Protocol | Early stage public preview: v0.9.1 is the 'Current' production release, v1.0 is a release 'Candidate', v0.8 is legacy | a2ui-project (Google-originated, open-source on GitHub; Apache-2.0) |
| Agent-User Interaction Protocol | Present | Protocol | Open, lightweight, event-based protocol; described by its maintainers as the general-purpose, bi-directional connection between a user-facing application and any agentic backend | AG-UI open-source project (github.com/ag-ui-protocol), originated and still primarily stewarded by CopilotKit; biweekly public working group |
| MCP Apps | Present | Protocol | Active extension to MCP; own repo describes it as extending 'the Model Context Protocol by letting tools declare UI resources' | modelcontextprotocol GitHub org (ext-apps sub-project); same umbrella as core MCP, which is now stewarded by the Agentic AI Foundation / Linux Foundation per this site's existing 'mcp' record |
| Agent Readability Spec | Read | Protocol | A specification and scoring checklist, not a protocol; framed as best practices to implement voluntarily | Vercel; published in Vercel's own Knowledge Base with no external standards process |
| AGENTS.md | Read | Protocol | "An open format... regardless of which coding agent you use"; explicitly not proprietary to any one tool | Agentic AI Foundation (AAIF), a Linux Foundation project |
| Apache Ossie (formerly Open Semantic Interchange) | Read | Protocol | Undergoing incubation at the Apache Software Foundation ('Apache Ossie (incubating)'); not yet a top-level ASF project. Core spec is marked DRAFT. | Apache Software Foundation, Apache Incubator (Ossie Podling Project Management Committee); formerly a Snowflake-led multi-vendor working group |
| llms.txt | Read | Protocol | "This is v2 of the proposal" — explicitly a community proposal open for input, not a standards-track document | Jeremy Howard / Answer.AI; maintained as an open proposal in the AnswerDotAI/llms-txt GitHub repository with a public Discord for implementation discussion |
| Open Knowledge Format | Read | Protocol | "An open specification; contributions, alternative implementations, and adoption beyond Google products are all explicitly welcomed" | Google Cloud open-source project; canonical repository is GoogleCloudPlatform/open-knowledge-format on GitHub (moved out of the GoogleCloudPlatform/knowledge-catalog monorepo in August 2026, which now carries only a frozen, unmaintained snapshot) |