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.
Card unusable as it stands
An agent reading this card cannot act on it.
What the card declares
- Name
- Frontman
- Agent version
- 1.0.0
- Transport
- JSONRPC
- Endpoint
- https://frontman.sh
- Card shape
- pre-v1.0
- Location
- standard location
- Skills
- 3
- Response time
- 138 ms
Findings
- ErrorRequired field missing: protocolVersion
protocolVersion - ErrorRequired field missing: provider.organization
provider.organization - WarningCard written in the shape used before v1.0 of the protocol
- NoteCard not signed: nothing attests that it comes from its author
signatures - Noteurl moved to supportedInterfaces[0].url in v1.0
url
Declared skills
- Visual website editingSelect live website elements and request WordPress updates or source-code changes using runtime context.
- Runtime context collectionCollect DOM, CSS, screenshots, CMS or component context, routes, and server logs for website editing agents.
- Lighthouse auditsRun performance and accessibility audits inside the Frontman workflow.
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://frontman.sh)HTML
<a href="https://kopass.app/a2a/validator?url=https://frontman.sh"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly9mcm9udG1hbi5zaA.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: 225 agents followed, 218 of which answered on the last pass.