Proposal: Clarify and Broaden Language Around .well-known-Based Discovery Mechanisms

[ognis1205]

As different .well-known-based discovery mechanisms continue to emerge—such as the Open Resource Descriptor (ORD) and the API Catalog—it’s important to clarify that multiple viable approaches exist and may be appropriate depending on the context.

Current Wording

The current wording in the spec—specifically the line:

This is a recommended approach for public agents or agents intended for broad discoverability within a specific domain.

—is taken from the official agent discovery documentation. However, this phrasing could be misleading, as it implies a single recommended discovery approach, while in reality multiple diverse discovery mechanisms exist and are valid.

Suggested Update

Clarify that:

• Multiple .well-known-based discovery mechanisms exist and may be suitable depending on deployment needs.
• The A2A community has chosen to register .well-known/agent-card.json with IANA.
• Other mechanisms like ORD and the API Catalog may be more appropriate in contexts such as hosting multiple agents under a single domain.

Additional Suggestion

• ORD
• API Catalog

[ognis1205]

cc: @darrelmiller @Fannon

SEE ALSO: #166