{
  "slug": "a2a-agent-discovery-without-a-registry",
  "title": "How Do Agents Discover A2A Agents Without a Standard Registry?",
  "description": "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.",
  "kind": "sub",
  "order": 8,
  "target_query": "how do agents discover A2A agents",
  "secondary_queries": [],
  "tags": [
    "a2a",
    "agent-card",
    "discovery",
    "registry",
    "well-known",
    "multi-agent",
    "interoperability"
  ],
  "published": "2026-11-06",
  "updated": "2026-11-06",
  "words": 950,
  "estimated_tokens": 1264,
  "premium": false,
  "rights": {
    "access": "free",
    "note": "Editorial guides are always free and never part of the licensed corpus.",
    "license": "https://changegamer.ai/license.xml",
    "pricing": "https://changegamer.ai/api/pricing.json",
    "payment": "https://changegamer.ai/api/payment.json"
  },
  "license": "https://changegamer.ai/license.xml",
  "citation": "ChangeGamer (2026-11-06). How Do Agents Discover A2A Agents Without a Standard Registry?. ChangeGamer. https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry (updated 2026-11-06).",
  "bibtex": "@misc{changegamer_a2a_agent_discovery_without_a_registry, title = {How Do Agents Discover A2A Agents Without a Standard Registry?}, publisher = {ChangeGamer}, year = {2026}, url = {https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry}, note = {Updated 2026-11-06}}",
  "canonical": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry",
  "markdown": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry.md",
  "takeaways": [
    "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."
  ],
  "outline": [
    {
      "depth": 2,
      "text": "What are the three ways to discover an A2A agent?",
      "anchor": "what-are-the-three-ways-to-discover-an-a2a-agent",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#what-are-the-three-ways-to-discover-an-a2a-agent"
    },
    {
      "depth": 2,
      "text": "How does well-known URI discovery work?",
      "anchor": "how-does-well-known-uri-discovery-work",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#how-does-well-known-uri-discovery-work"
    },
    {
      "depth": 2,
      "text": "Does the A2A specification define a registry?",
      "anchor": "does-the-a2a-specification-define-a-registry",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#does-the-a2a-specification-define-a-registry"
    },
    {
      "depth": 3,
      "text": "Which registries exist for A2A today?",
      "anchor": "which-registries-exist-for-a2a-today",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#which-registries-exist-for-a2a-today"
    },
    {
      "depth": 2,
      "text": "Can the MCP Registry or ERC-8004 be used to discover A2A agents?",
      "anchor": "can-the-mcp-registry-or-erc-8004-be-used-to-discover-a2a-agents",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#can-the-mcp-registry-or-erc-8004-be-used-to-discover-a2a-agents"
    },
    {
      "depth": 2,
      "text": "How should you choose between the three routes?",
      "anchor": "how-should-you-choose-between-the-three-routes",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#how-should-you-choose-between-the-three-routes"
    },
    {
      "depth": 2,
      "text": "What should a discoverable card not reveal?",
      "anchor": "what-should-a-discoverable-card-not-reveal",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#what-should-a-discoverable-card-not-reveal"
    },
    {
      "depth": 2,
      "text": "Is ChangeGamer discoverable as an A2A agent?",
      "anchor": "is-changegamer-discoverable-as-an-a2a-agent",
      "url": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry#is-changegamer-discoverable-as-an-a2a-agent"
    }
  ],
  "faq": [
    {
      "question": "Is there an official A2A agent registry?",
      "answer": "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."
    },
    {
      "question": "Where is an A2A Agent Card published?",
      "answer": "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."
    },
    {
      "question": "Can I search for A2A agents by skill?",
      "answer": "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."
    },
    {
      "question": "Is the MCP Registry a registry for A2A agents?",
      "answer": "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."
    }
  ],
  "body": "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](/resources/a2a-protocol) holds the wire contract; this article is the decision between the routes. The [pillar](/articles/a2a-protocol-in-practice) covers the protocol as a whole.\n\n## What are the three ways to discover an A2A agent?\n\nThe three strategies are the well-known URI, curated registries and direct configuration, and they differ in who has to know what in advance.\n\n| Strategy | Client must already know | Best fit |\n|---|---|---|\n| Well-known URI | A domain | Public agents, broad discovery within a domain |\n| Curated registry | A registry endpoint | Searching by skill, tag, provider or capability, with central governance |\n| Direct configuration | The card location itself | Static, tightly coupled systems |\n\nThe 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.\n\n## How does well-known URI discovery work?\n\nA client appends a fixed path to a domain and fetches it. The [A2A protocol reference](/resources/a2a-protocol) (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.\n\n```bash\n# Fetch a card; replace the domain with one you are allowed to query\ncurl -sS -H 'Accept: application/json' https://agents.example.org/.well-known/agent-card.json | head -c 600\n```\n\nTwo 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](/articles/a2a-agent-card-design).\n\n## Does the A2A specification define a registry?\n\nNo, 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.\"\n\nThe 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.\n\n### Which registries exist for A2A today?\n\nBecause 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.\n\n## Can the MCP Registry or ERC-8004 be used to discover A2A agents?\n\nNo, 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](/resources/mcp-registry), updated 4 September 2026). It does not list A2A agents.\n\nERC-8004 is an onchain registration scheme for agents, and the [ERC-8004 reference](/resources/erc-8004-trustless-agents) 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](/resources/mcp-vs-a2a) covers how the two protocols divide the work. For making a paid API findable by agents more broadly, see [discoverability for paid agent APIs](/articles/discoverability-for-paid-agent-apis).\n\n## How should you choose between the three routes?\n\nChoose 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:\n\n1. List the agents you actually need to call. If the list is short and stable, configure the card URLs directly and stop.\n2. If the partners are named domains, fetch each `/.well-known/agent-card.json` and cache the result, refreshing when the card changes.\n3. 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.\n4. Whatever route found the card, apply the checks in [trusting a remote agent](/articles/trusting-a-remote-agent) before delegating, because discovery says where an agent is, not whether to trust it.\n\n## What should a discoverable card not reveal?\n\nA 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.\"\n\n- Protect the card endpoint with mTLS, IP restrictions or OAuth when the card is not meant to be public.\n- Put sensitive detail in the authenticated extended card (the `extendedAgentCard` capability), not the public one.\n- A registry can apply selective disclosure, showing different parties different cards.\n\nAuthentication options are compared in [A2A authentication schemes](/articles/a2a-authentication-schemes).\n\n## Is ChangeGamer discoverable as an A2A agent?\n\nNo. 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.",
  "cluster": {
    "id": "a2a-in-practice",
    "title": "A2A in practice: agent-to-agent interoperability",
    "description": "How to build, secure and run agent-to-agent delegation with the A2A protocol — when A2A beats in-process subagents, Agent Cards, task lifecycle, bindings, authentication, credential propagation across hops, discovery and trust, v0.3 to v1.0 migration, framework support and failure handling — not MCP tool serving (mcp-in-practice) and not single-agent identity (agent-identity-and-authentication-for-ai-agents).",
    "status": "complete",
    "pillar": {
      "slug": "a2a-protocol-in-practice",
      "title": "The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It",
      "description": "A practical guide to the A2A (Agent2Agent) protocol: what it standardizes, when it beats in-process subagents, how Agent Cards, task states, bindings and authentication work, how credentials cross agent hops, and how to launch it.",
      "kind": "pillar",
      "order": 0,
      "html": "https://changegamer.ai/articles/a2a-protocol-in-practice",
      "markdown": "https://changegamer.ai/articles/a2a-protocol-in-practice.md",
      "json": "https://changegamer.ai/api/articles/a2a-protocol-in-practice.json"
    },
    "articles": [
      {
        "slug": "do-you-need-a2a",
        "title": "Do You Need A2A for a Multi-Agent System? A Decision Rule",
        "description": "A decision rule for choosing between in-process subagents and the A2A protocol: start with one agent, add more only for a named failure, and cross the network with A2A only when a remote party, framework or trust boundary demands it.",
        "kind": "sub",
        "order": 1,
        "html": "https://changegamer.ai/articles/do-you-need-a2a",
        "markdown": "https://changegamer.ai/articles/do-you-need-a2a.md",
        "json": "https://changegamer.ai/api/articles/do-you-need-a2a.json"
      },
      {
        "slug": "a2a-agent-card-design",
        "title": "Designing an Agent Card: What Goes in the Public Card and What Waits",
        "description": "How to design an A2A Agent Card: the field groups, the well-known path, optional signing, and a rule for splitting what the public card advertises from what an authenticated client fetches in the extended card.",
        "kind": "sub",
        "order": 2,
        "html": "https://changegamer.ai/articles/a2a-agent-card-design",
        "markdown": "https://changegamer.ai/articles/a2a-agent-card-design.md",
        "json": "https://changegamer.ai/api/articles/a2a-agent-card-design.json"
      },
      {
        "slug": "a2a-task-lifecycle",
        "title": "A2A Task States and Operations: What Each State Means for an Orchestrator",
        "description": "The eight A2A task states, the eleven operations that act on tasks, the difference between interrupted and terminal states, and an inference-labelled handler matrix for an orchestrator.",
        "kind": "sub",
        "order": 3,
        "html": "https://changegamer.ai/articles/a2a-task-lifecycle",
        "markdown": "https://changegamer.ai/articles/a2a-task-lifecycle.md",
        "json": "https://changegamer.ai/api/articles/a2a-task-lifecycle.json"
      },
      {
        "slug": "a2a-bindings-json-rpc-grpc-rest",
        "title": "A2A JSON-RPC vs gRPC vs REST: What Differs Between the Three Bindings",
        "description": "The three A2A protocol bindings (JSON-RPC, gRPC, HTTP+JSON/REST): what the specification keeps identical, what differs on the wire, and an inference-labelled guide to picking one.",
        "kind": "sub",
        "order": 4,
        "html": "https://changegamer.ai/articles/a2a-bindings-json-rpc-grpc-rest",
        "markdown": "https://changegamer.ai/articles/a2a-bindings-json-rpc-grpc-rest.md",
        "json": "https://changegamer.ai/api/articles/a2a-bindings-json-rpc-grpc-rest.json"
      },
      {
        "slug": "a2a-authentication-schemes",
        "title": "A2A Authentication Schemes: Which to Declare in Your Agent Card",
        "description": "The five security scheme families an A2A Agent Card can declare (API key, HTTP auth, OAuth 2.0, OpenID Connect, mutual TLS), an inference-labelled rule for choosing one, and how a client handles auth-required tasks.",
        "kind": "sub",
        "order": 5,
        "html": "https://changegamer.ai/articles/a2a-authentication-schemes",
        "markdown": "https://changegamer.ai/articles/a2a-authentication-schemes.md",
        "json": "https://changegamer.ai/api/articles/a2a-authentication-schemes.json"
      },
      {
        "slug": "credential-propagation-across-agent-hops",
        "title": "Credential Propagation Across Agent Hops: Exchange, Audience and Depth",
        "description": "How to carry authority through a chain of delegating agents: why forwarding a token fails, per-hop RFC 8693 exchange with act and may_act, RFC 8707 audience binding, a worked sequence and a failure walk-through.",
        "kind": "sub",
        "order": 6,
        "html": "https://changegamer.ai/articles/credential-propagation-across-agent-hops",
        "markdown": "https://changegamer.ai/articles/credential-propagation-across-agent-hops.md",
        "json": "https://changegamer.ai/api/articles/credential-propagation-across-agent-hops.json"
      },
      {
        "slug": "trusting-a-remote-agent",
        "title": "How to Verify a Remote A2A Agent Before Delegating",
        "description": "What a signed Agent Card proves and does not, how domain, key and ERC-8004 identity differ, where Web Bot Auth fits, and why card text and returned artifacts are untrusted input, ending in an ordered checklist.",
        "kind": "sub",
        "order": 7,
        "html": "https://changegamer.ai/articles/trusting-a-remote-agent",
        "markdown": "https://changegamer.ai/articles/trusting-a-remote-agent.md",
        "json": "https://changegamer.ai/api/articles/trusting-a-remote-agent.json"
      },
      {
        "slug": "a2a-agent-discovery-without-a-registry",
        "title": "How Do Agents Discover A2A Agents Without a Standard Registry?",
        "description": "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.",
        "kind": "sub",
        "order": 8,
        "html": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry",
        "markdown": "https://changegamer.ai/articles/a2a-agent-discovery-without-a-registry.md",
        "json": "https://changegamer.ai/api/articles/a2a-agent-discovery-without-a-registry.json"
      },
      {
        "slug": "a2a-v0-3-to-v1-0-migration",
        "title": "Migrate A2A v0.3 to v1.0: An Ordered Checklist for Clients and Servers",
        "description": "An ordered checklist for moving an A2A client or server from v0.3 to v1.0: the A2A-Version header rule, method names, Part shape, a runnable grep check, and symptom-to-cause pointers.",
        "kind": "sub",
        "order": 9,
        "html": "https://changegamer.ai/articles/a2a-v0-3-to-v1-0-migration",
        "markdown": "https://changegamer.ai/articles/a2a-v0-3-to-v1-0-migration.md",
        "json": "https://changegamer.ai/api/articles/a2a-v0-3-to-v1-0-migration.json"
      },
      {
        "slug": "agent-frameworks-with-a2a-support",
        "title": "Does Your Agent Framework Really Support A2A? How to Read the Claim and What to Test",
        "description": "Which agent frameworks list A2A support, what native, add-on, platform-gated and unrecorded mean, a short test checklist to run before you rely on it, and how that differs from the protocol's own SDKs.",
        "kind": "sub",
        "order": 10,
        "html": "https://changegamer.ai/articles/agent-frameworks-with-a2a-support",
        "markdown": "https://changegamer.ai/articles/agent-frameworks-with-a2a-support.md",
        "json": "https://changegamer.ai/api/articles/agent-frameworks-with-a2a-support.json"
      },
      {
        "slug": "failure-handling-across-agent-boundaries",
        "title": "Failed or Rejected Remote A2A Task: Retry, Degrade or Surface?",
        "description": "How to decide what happens after a remote A2A task ends badly: the side-effects test that splits failed into retry or surface, why rejected is not a retry case, why input-required is not a failure, and a structured result for the caller.",
        "kind": "sub",
        "order": 11,
        "html": "https://changegamer.ai/articles/failure-handling-across-agent-boundaries",
        "markdown": "https://changegamer.ai/articles/failure-handling-across-agent-boundaries.md",
        "json": "https://changegamer.ai/api/articles/failure-handling-across-agent-boundaries.json"
      },
      {
        "slug": "a2a-production-launch-checklist",
        "title": "A2A Production Launch Checklist: Gates to Pass Before You Ship",
        "description": "A go/no-go checklist for launching A2A agent-to-agent delegation, one line per gate, each pointing to the article that owns the detail: need, card, states, binding, auth, trust, versioning, failure.",
        "kind": "sub",
        "order": 12,
        "html": "https://changegamer.ai/articles/a2a-production-launch-checklist",
        "markdown": "https://changegamer.ai/articles/a2a-production-launch-checklist.md",
        "json": "https://changegamer.ai/api/articles/a2a-production-launch-checklist.json"
      }
    ]
  },
  "navigation": {
    "pillar": {
      "slug": "a2a-protocol-in-practice",
      "title": "The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It",
      "description": "A practical guide to the A2A (Agent2Agent) protocol: what it standardizes, when it beats in-process subagents, how Agent Cards, task states, bindings and authentication work, how credentials cross agent hops, and how to launch it.",
      "kind": "pillar",
      "order": 0,
      "html": "https://changegamer.ai/articles/a2a-protocol-in-practice",
      "markdown": "https://changegamer.ai/articles/a2a-protocol-in-practice.md",
      "json": "https://changegamer.ai/api/articles/a2a-protocol-in-practice.json"
    },
    "previous": {
      "slug": "trusting-a-remote-agent",
      "title": "How to Verify a Remote A2A Agent Before Delegating",
      "description": "What a signed Agent Card proves and does not, how domain, key and ERC-8004 identity differ, where Web Bot Auth fits, and why card text and returned artifacts are untrusted input, ending in an ordered checklist.",
      "kind": "sub",
      "order": 7,
      "html": "https://changegamer.ai/articles/trusting-a-remote-agent",
      "markdown": "https://changegamer.ai/articles/trusting-a-remote-agent.md",
      "json": "https://changegamer.ai/api/articles/trusting-a-remote-agent.json"
    },
    "next": {
      "slug": "a2a-v0-3-to-v1-0-migration",
      "title": "Migrate A2A v0.3 to v1.0: An Ordered Checklist for Clients and Servers",
      "description": "An ordered checklist for moving an A2A client or server from v0.3 to v1.0: the A2A-Version header rule, method names, Part shape, a runnable grep check, and symptom-to-cause pointers.",
      "kind": "sub",
      "order": 9,
      "html": "https://changegamer.ai/articles/a2a-v0-3-to-v1-0-migration",
      "markdown": "https://changegamer.ai/articles/a2a-v0-3-to-v1-0-migration.md",
      "json": "https://changegamer.ai/api/articles/a2a-v0-3-to-v1-0-migration.json"
    }
  },
  "resources": [
    {
      "slug": "a2a-protocol",
      "html": "https://changegamer.ai/resources/a2a-protocol",
      "markdown": "https://changegamer.ai/resources/a2a-protocol.md",
      "json": "https://changegamer.ai/api/resources/a2a-protocol.json"
    },
    {
      "slug": "mcp-vs-a2a",
      "html": "https://changegamer.ai/resources/mcp-vs-a2a",
      "markdown": "https://changegamer.ai/resources/mcp-vs-a2a.md",
      "json": "https://changegamer.ai/api/resources/mcp-vs-a2a.json"
    },
    {
      "slug": "mcp-registry",
      "html": "https://changegamer.ai/resources/mcp-registry",
      "markdown": "https://changegamer.ai/resources/mcp-registry.md",
      "json": "https://changegamer.ai/api/resources/mcp-registry.json"
    },
    {
      "slug": "erc-8004-trustless-agents",
      "html": "https://changegamer.ai/resources/erc-8004-trustless-agents",
      "markdown": "https://changegamer.ai/resources/erc-8004-trustless-agents.md",
      "json": "https://changegamer.ai/api/resources/erc-8004-trustless-agents.json"
    }
  ]
}