Registering your agent so other agents can find it

The honest starting point

Many articles talk about registering an agent as if there were one directory to submit it to. There is not. The A2A specification describes how discovery works, and says plainly that it does not prescribe a standard API for registries; building them is left to whoever runs one.

So registration today is mostly publishing: putting an accurate card where agents already know to look, and listing it anywhere that the agents you care about actually search.

The three ways agents find each other

Well-known address. An agent that knows your domain fetches https://your-domain/.well-known/agent-card.json. This is the default, it needs nothing but a published file, and it is the one to do first.

Curated registries. A company, platform, or industry group runs a catalogue of agent cards and lets agents search it. Some are private to one organization; public ones are emerging. Listing yours in a registry relevant to your industry is worth doing when one exists.

Direct configuration. A partner hard-codes your endpoint into their own agent. This is how most business-to-business integrations start, and it needs only that you give them your card's address.

Make the card easy to find from your own site

Mention the card's address in your site's llms.txt file, the plain-text index agents increasingly read. Keep the card in the same place permanently, serve it with a JSON content type, and allow cross-origin requests to it so browser-based agents can read it.

Keep it true over time

A registered card that describes a skill you retired, or an endpoint that moved, damages trust faster than having no card. Put the card under the same review as your website: when a service changes, the card changes the same day.