Discussion on agent discovery mechanisms — do you have any better proposals?

Dear all,

I originally wanted to discuss the issue of *agent discovery* at our last
meeting, but we ran out of time. Let’s continue the discussion here by
email. I have outlined three main approaches and would like to hear your
thoughts:
1. Based on RFC 8615 (.well-known path)

Place a standardized file under the domain’s /.well-known/ path to declare
the agents available under that domain.

   -

   *Pros*: Mature standard, easy to deploy, compatible with DNS/TLS,
   decentralized.
   -

   *Cons*: Limited to existing domains, lacks global indexing, less
   friendly for individual users without domains.

2. Global Registration Center

Establish a centralized registry for agents, such as an MCP Registry or an
Agent Name Service (ANS).

   -

   *Pros*: Strong discoverability, good user experience, standardized
   naming and classification, easier governance.
   -

   *Cons*: Higher centralization risks, requires governance and
   maintenance, may introduce entry barriers, scalability challenges.

3. Blockchain-like Decentralized Approach

Use decentralized infrastructures such as blockchain, DHT, IPFS, or ENS to
store and discover agent information.

   -

   *Pros*: Decentralized, censorship-resistant, data integrity, global
   discoverability, can integrate with DID/VC systems.
   -

   *Cons*: Complex to implement, performance and cost issues, ecosystem
   still immature.

Which approach do you prefer?


Best regards,
Gaowei Chang