Can other agents read your agent card?
An agent introduces itself with a card published at /.well-known/agent-card.json. It is the only document another agent reads before deciding to call you. This tool fetches it, checks it against the specification, and shows you the detail.
Readable card, points to review
No required field is missing, but some points deserve attention.
What the card declares
- Name
- Handler
- Provider
- Handler
- Agent version
- 1.0.0
- Protocol version
- 0.3
- Transport
- HTTP+JSON
- Endpoint
- https://handler.alduncanson.com/
- Card shape
- v1.0
- Location
- standard location
- Skills
- 1
- Response time
- 168 ms
Findings
- WarningRequired field empty: skills[0].tags
skills[0].tags - NoteCard not signed: nothing attests that it comes from its author
signatures
Declared skills
- HandlerUse Handler when you need to interact with A2A protocol agents: send messages and manage tasks from CLI scripts, configure production authentication (bearer tokens, API keys, mTLS, OAuth2), inspect agent cards, stream task events, or expose A2A operations as MCP tools for other agents.
Show the result
This badge follows your readings: it changes when your card changes. Paste it in your README.
Markdown
[](https://kopass.app/a2a/validator?url=https://handler.alduncanson.com)HTML
<a href="https://kopass.app/a2a/validator?url=https://handler.alduncanson.com"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly9oYW5kbGVyLmFsZHVuY2Fuc29uLmNvbQ.svg" alt="A2A card" height="20"></a>The rules come from the protocol's specification/a2a.proto file, where every required field is marked as such. Nothing is added.
Cards read here feed the KoPass daily reading: 210 agents followed, 209 of which answered on the last pass.