A news wire on how AI agents pay and get paid.
links + original short summaries; content belongs to publishers
23 entries. All categories. JSON: /api/library/agent-protocols.json.
Merged MCP enhancement proposal for pre-connection discovery of remote MCP servers through Server Cards, advertised from a domain-level /.well-known/ai-catalog.json. It supersedes the earlier SEP-1649 approach. The server-card schema is still marked experimental.
Latest dated version of the Model Context Protocol specification, covering architecture, base protocol, lifecycle, transports, authorization and client and server features. The version identifier is the date.
Internet-Draft for publishing AI agent endpoints and capability metadata in DNS using SVCB records and DNS-SD-style indexes, with DNSSEC/DANE for validation. Active individual draft, revision 02.
Cloudflare post introducing an Agent Readiness score and the isitagentready.com scanner, which checks emerging standards such as llms.txt, Markdown negotiation, Content Signals, RFC 9727 API catalogs, MCP Server Cards, A2A Agent Cards, Agent Skills and the x402/MPP commerce protocols.
Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.
Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.
Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.
Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.
IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).
Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.
Source, OpenAPI reference and server.json schema for the community-driven MCP Registry, including the publishing flow and namespace verification.
Experimental extension that holds the TypeScript and JSON Schema source for MCP Server Cards. A card describes a remote server's identity and transport endpoints; tools are listed at runtime, not on the card.
Cross-protocol draft standard for a typed, nestable JSON catalog that lists heterogeneous AI artifacts (MCP servers, A2A agents, datasets and more) for discovery. It is developed by members of several AI protocol communities.
A2A guidance on finding agents through a well-known Agent Card URL (/.well-known/agent-card.json), curated registries, or direct configuration. It notes that the spec does not prescribe a registry API.
Free public registry of A2A agents that is itself discoverable as an A2A agent. It offers natural-language agent search and DNS- and GitHub-based verification, and its agent card includes an extension that declares a payment model.
agents.json, an OpenAPI-based contract published at /.well-known/agents.json that describes multi-step API 'flows' for agents, linking the outputs of one operation to the inputs of the next.
Open format for packaging agent capabilities as SKILL.md files with YAML frontmatter, plus a discovery index schema used by sites at /.well-known/agent-skills/index.json (for example docs.x402.org and mpp.dev).
Simple open format for a README-style instruction file aimed at coding agents. mpp.dev publishes one and links it from its API catalog.
Standards-track RFC (June 2025) defining /.well-known/api-catalog and the api-catalog link relation, which return a linkset of a publisher's APIs with links to their descriptions, docs and status endpoints.
Standards-track RFC (April 2025) defining metadata that a protected resource publishes so clients can learn how to obtain tokens for it. Remote MCP authorization relies on it.
robots.txt extension (Content-Signal: search=, ai-input=, ai-train=) that declares how crawled content may be used, settable per user-agent. mpp.dev, x402scan and x402.org use it.
Community Group proposal that lets a web page register tools for in-browser agents (document.modelContext.registerTool with a JSON Schema input). It is a CG draft, not a W3C standard.
Large MCP server and remote connector directory, described as a superset of the official MCP Registry. Each server is scanned and scored, and the directory has a public REST API with OpenAPI and an RFC 9727 api-catalog.