ChangeGamer

How Do Agents Discover A2A Agents Without a Standard Registry?

Part 8 of A2A in practice: agent-to-agent interoperability · 950 words · ~4 min read · published · updated · Markdown variant

The three discovery strategies in the A2A documentation, why the spec prescribes no registry API, what vendor registries fill the gap, and how to choose between a well-known URI, a registry and direct configuration.

In short

  • A2A agents are discovered in three ways: fetching the Agent Card from a well-known URI on a known domain, querying a curated registry, or using directly configured card locations.
  • The A2A documentation, read on 6 November 2026, states that the current specification does not prescribe a standard API for curated registries, so any registry a client uses is a vendor, open source or in-house design with its own interface.
  • An A2A server must publish its Agent Card at https://{server_domain}/.well-known/agent-card.json, which makes domain-based discovery the one mechanism every A2A agent is required to support (inference: registries are optional extras).
  • The well-known URI answers only the question of what a given domain offers, so finding agents by skill or capability across many domains needs a registry or a crawl of your own.
  • Any Agent Card containing sensitive data must be protected with authentication and authorization, so a public well-known card should hold only what you are willing to show to anyone.

Part of the The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It guide.


Agents discover A2A agents by one of three routes: fetching a well-known URL on a domain, searching a curated registry, or reading card locations from configuration. The A2A documentation's agent discovery page (https://a2a-protocol.org/latest/topics/agent-discovery/, read 6 November 2026) lists exactly these. The A2A protocol reference holds the wire contract; this article is the decision between the routes. The pillar covers the protocol as a whole.

What are the three ways to discover an A2A agent?

The three strategies are the well-known URI, curated registries and direct configuration, and they differ in who has to know what in advance.

Strategy Client must already know Best fit
Well-known URI A domain Public agents, broad discovery within a domain
Curated registry A registry endpoint Searching by skill, tag, provider or capability, with central governance
Direct configuration The card location itself Static, tightly coupled systems

The documentation recommends the well-known URI for public agents and broad discovery within a domain, and describes it as simple and standards-based. It describes direct configuration (hardcoded values, config files, environment variables or proprietary APIs) as fine for static, tightly coupled systems, with the cost that a changed card means reconfiguring clients.

How does well-known URI discovery work?

A client appends a fixed path to a domain and fetches it. The A2A protocol reference (updated 27 October 2026) states that an agent MUST publish an Agent Card at https://{server_domain}/.well-known/agent-card.json, a path that v0.3.0 renamed from agent.json. The convention comes from RFC 8615.

# Fetch a card; replace the domain with one you are allowed to query
curl -sS -H 'Accept: application/json' https://agents.example.org/.well-known/agent-card.json | head -c 600

Two limits follow from the design. First, the client needs the domain already, so this route is lookup, not search. Second, one domain means one card path, so a company with many agents has to decide how its agents map to cards and hostnames (inference). Card contents are covered in Agent Card design.

Does the A2A specification define a registry?

No, the A2A specification does not define a registry API. The documentation says: "The current A2A specification does not prescribe a standard API for curated registries."

The same page describes what a curated registry would do: a central service stores cards, clients search by skills, tags, provider or capabilities, and servers publish to it. Its stated benefits are centralized governance, capability search and access control, and its stated cost is ongoing maintenance. Because no interface is prescribed, a client written for one registry will not work against another without an adapter (inference). Plan for that before you depend on a registry in code.

Which registries exist for A2A today?

Because the specification leaves the registry interface open, any registry carries its own query API. Vendor registries exist outside the specification; this article names none because none was verified against its own documentation. Check any candidate's documentation before choosing one, and expect lock-in to that vendor's query API.

Can the MCP Registry or ERC-8004 be used to discover A2A agents?

No, the MCP Registry and ERC-8004 are not A2A registries, but both show what the alternatives look like. The MCP Registry at registry.modelcontextprotocol.io lists MCP servers, with metadata stored in a server.json manifest (MCP Registry reference, updated 4 September 2026). It does not list A2A agents.

ERC-8004 is an onchain registration scheme for agents, and the ERC-8004 reference records it as a Draft standard. It concerns agent identity and registration, but it is a separate system, not part of A2A, and nothing on the A2A agent-discovery page points clients to it. The MCP vs A2A reference covers how the two protocols divide the work. For making a paid API findable by agents more broadly, see discoverability for paid agent APIs.

How should you choose between the three routes?

Choose the well-known URI when you know the domain, a registry when you must search across many publishers, and configuration when the set of agents is fixed. A practical sequence:

  1. List the agents you actually need to call. If the list is short and stable, configure the card URLs directly and stop.
  2. If the partners are named domains, fetch each /.well-known/agent-card.json and cache the result, refreshing when the card changes.
  3. Only if you need search across unknown publishers, adopt a registry, and wrap it behind your own small interface so a different registry can replace it.
  4. Whatever route found the card, apply the checks in trusting a remote agent before delegating, because discovery says where an agent is, not whether to trust it.

What should a discoverable card not reveal?

A discoverable card should not reveal anything you would not show an anonymous visitor. The documentation warns that cards can expose internal URLs and sensitive skill descriptions, and states: "Any Agent Card containing sensitive data must be protected with authentication and authorization mechanisms."

Authentication options are compared in A2A authentication schemes.

Is ChangeGamer discoverable as an A2A agent?

No. As of 6 November 2026, ChangeGamer speaks MCP and publishes no agent-card.json. Its /.well-known/ directory holds api-catalog, mcp.json, mcp/server-card.json, agent-access.json and security.txt, and the BACKLOG entry of 16 September 2026 records the decision not to publish an A2A card. Everything above comes from the A2A documentation and the cited references, and none of it from running an A2A deployment.

Frequently asked questions

Is there an official A2A agent registry?
No official registry API exists in the A2A specification: the A2A documentation, read on 6 November 2026, says the current specification does not prescribe a standard API for curated registries. Any registry a client uses defines its own interface, because the specification leaves that interface open.
Where is an A2A Agent Card published?
An A2A server publishes its Agent Card at https://{server_domain}/.well-known/agent-card.json, following the well-known URI convention of RFC 8615. A client that knows a domain can fetch that single URL to learn the agent skills, endpoints and security requirements.
Can I search for A2A agents by skill?
Searching A2A agents by skill needs a curated registry, because the well-known URI only describes one domain at a time. The A2A documentation says registry clients can search by skills, tags, provider or capabilities, but the query API is not standardized.
Is the MCP Registry a registry for A2A agents?
The MCP Registry at registry.modelcontextprotocol.io catalogs Model Context Protocol servers, not A2A agents, so it cannot be used to discover A2A Agent Cards. It is a useful comparison for what a curated catalog looks like, nothing more.

#a2a #agent-card #discovery #registry #well-known #multi-agent #interoperability

Put this corpus inside your own agents

This guide is free and stays free. The reference corpus behind it — machine-readable contracts, verified primary sources, continuously refreshed — is the paid product: a €5 starter key unlocks every premium reference for one agent via API; a €25 corpus license delivers the full corpus as RAG / fine-tuning data with an explicit AI-use grant; the €150 enterprise license adds commercial redistribution rights.

Agents: this page as Markdown · JSON · offers at /api/pricing.json · payment methods at /api/payment.json · single-resource access via HTTP 402 (how that works)