Discovery · DNS
Two Well-Known URIs, Same Week: Agent Discovery Gets a Second Front Door
On October 6, the Model Context Protocol finalized its MCP Server Cards spec — and in doing so, made a deliberate choice not to invent its own discovery location. Instead, MCP pointed to an AI Catalog format being developed by the A2A project, published at a shared well-known path. The same day, Sierra and Meta announced the Personal Agent Protocol, nicknamed "Poppy," whose draft 0.1 specification requires companies to publish a separate document at their own well-known path for personal agents to find.
The coincidence is notable less for the overlap than for the restraint on one side and the divergence on the other. MCP deferring to A2A's catalog format is an unusual move in a space where every new spec has tended to claim its own namespace and discovery convention. It suggests at least two of the major agent-protocol efforts are converging on a shared answer to "where does an agent look to find out what a domain offers." But Poppy's arrival on the same day, with its own separate well-known file aimed specifically at consumer-facing commerce agents, shows that convergence isn't universal — it's happening within the enterprise/tool-calling lineage (MCP, A2A) while a different lineage (consumer agent commerce, backed by Sierra, Meta, Shopify, Stripe, Walmart) is standing up its own door.
For any domain trying to be agent-legible, this means maintaining two separate discovery surfaces: one listing MCP servers and A2A-compatible agents, another listing personal-agent-facing capabilities for commerce tasks. Neither is wrong on its own terms — a company's internal tool-calling agents and a customer's personal shopping agent are solving different problems — but it reproduces exactly the fragmentation that well-known-URI schemes were supposed to prevent. The test now is whether these two catalogs converge over the next year, or whether domains end up serving a small zoo of JSON files at /.well-known/, each legible to a different protocol family and invisible to the others.
This is a discovery-layer problem, not an identity or orchestration one: before an agent can authenticate itself or hand off a task, it has to know where to look. Right now, the answer depends on which lineage of protocol it was built on.