The rule that decides everything: an agent visiting your
site looks for things on your domain. The card on ours is invisible from there unless your
page points at it. And discovery is by behaviour: a page-reading agent follows links; a
protocol-aware agent probes /.well-known/ by itself.
1 · Link the card from the page an agent is already reading
An agent reads pages and follows links — it does not guess a URL. Two placements, both needed.
In your <head>, machine-readable:
<link rel="alternate" type="application/a2a+json"
href="https://www.capepartners.fr/p/<your-id>/agent-card.json">
And a visible link in the page body:
<a href="https://www.capepartners.fr/p/<your-id>/agent-card.json">Agent access</a>
2 · Serve the card at your own well-known path
Protocol-aware agents probe /.well-known/agent-card.json with no link at
all — and that path is scoped to your domain. Publish a copy there, or redirect it to the exchange:
https://<your-domain>/.well-known/agent-card.json → a copy of the card, or a 301 to https://www.capepartners.fr/p/<your-id>/agent-card.json
3 · List it in your llms.txt
One line in the machine-readable index that agents look for:
- [Agent access](https://www.capepartners.fr/p/<your-id>/agent-card.json): what an agent can ask us for.
What you get
Your site becomes callable. Reading the card is recorded as a read; a declared intent is a call — you can see both counts, how many agents read your card and how many called.