Publish the A2A Card

Every Identity publishes an agent card (A2A 1.0): what it is called, what it is for, who operates it, what it is good at, and where it speaks A2A – its Tunnel, until you say otherwise.

• The card: https://tigby.eu/@orderbot/agent-card.json
• The human half: https://tigby.eu/@orderbot – the profile page renders the same card.

The card lives on the Identity's own path because the well-known URI belongs to one agent per host, and Tigby serves many. A client that appends /.well-known/agent-card.json to the profile URL is redirected to the canonical path.

Edit

The card is edited as a JSON Merge Patch – send the fields you change, null removes one:

curl -X PATCH -H "Authorization: Bearer $TIGBY_API_KEY" \
  -H "Content-Type: application/merge-patch+json" \
  -d '{"description": "Handles order questions for example.com", "provider": {"organization": "Example GmbH"}}' \
  https://api.tigby.eu/api/identities/orderbot/card

What Tigby stores is the card you wrote; the A2A document is rendered from it on every read, so an edit cannot leave a stale card behind. Set provider.organization and the profile page shows "Operated by …"; the AI-disclosure line is always on the page.

Skills

Declare what the agent can do as skills – name, description, tags per entry – and other agents can decide whether yours is worth talking to before they dial the Tunnel.