Agents on the web
How does an agent find a service, understand its capabilities and choose an action? We examine the decisions behind the experience.
RESEARCH / AGENTIC WEB
We study the emerging Agentic Web: how agents discover, understand and act online. We test protocols before building useful experiences.
How does an agent find a service, understand its capabilities and choose an action? We examine the decisions behind the experience.
We test how tools, interfaces, identity, payments and commerce protocols work together. What is interoperable, and where does it break?
We test relevance, reliability and human control together. A successful tool call is one step in a successful experience.
This atlas presents protocols we research. Inclusion does not imply implementation or endorsement. Sources and dates show what we have verified.
OUR RESEARCH MAP
MCP runs through our research. Six constellations map interfaces, agents, discovery, trust, payments and commerce.
No verified public GitHub contributor list is available for this protocol.
Official sources and GitHub contributions where verified · atlas updated October 11, 2026. Existing contributor lists are from September 27, 2026. Individual profiles do not imply affiliation with the organizations shown.
A short definition for each protocol. In-depth profiles will follow.
An HTTP payment flow for machine-to-machine requests, including one-off charges and metered sessions.
Official specification ↗A way to request and authorize payment for an HTTP resource using the 402 response.
Official specification ↗Cryptographically signed mandates to express and verify payment authorization for agent transactions.
Official specification ↗A declarative format for agents to send interface components that a client renders.
Official specification ↗An event-based connection between an agentic backend and an interactive frontend.
Official specification ↗An MCP extension for delivering interactive interfaces from servers into host applications.
Official specification ↗An open protocol for asking a website questions in natural language and receiving structured answers; its implementation also exposes MCP.
Official specification ↗A common way for agents to access external tools, resources and context.
Official specification ↗An emerging browser API proposal for websites to expose structured actions to agents.
Official specification ↗A protocol for independent agents to discover each other, exchange tasks and collaborate.
Official specification ↗A shared-session layer that synchronizes agent state across multiple clients.
Official specification ↗A point-to-point protocol connecting code editors and coding agents.
Official specification ↗A secure, scalable messaging transport for agent systems, with bindings for protocols such as A2A and MCP.
Official specification ↗A proposal for publishing and discovering agents, tools and skills through federated catalogs with verifiable publisher metadata.
Official specification ↗An emerging protocol suite for agent identity, description, discovery and secure messaging; some parts remain drafts.
Official specification ↗An IETF draft for signing automated HTTP requests so a website can verify the caller’s identity.
Official specification ↗Poppy lets personal agents discover companies, sign users in and work through websites, APIs or company agents within agreed permissions. Draft 0.1, updated October 9, 2026; checked October 11, 2026. It may change before a stable release.
Official specification ↗Visa’s specification for an agent to prove its identity and commerce intent to a merchant using signed requests.
Official specification ↗A commerce interface for agents, merchants and payment providers to exchange shopping and checkout information.
Official specification ↗Shared commerce building blocks across product discovery, checkout and post-purchase.
Official specification ↗An environment to test emerging protocols and authorized partner access, then turn experiments into technology.
Our first field of application: agentic commerce.
See CartmelAIA QUESTION. AN IDEA. A FIRST STEP.
Platforms, product teams, researchers. Better experiences begin with a conversation.
Let’s talk