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.
Conformant card
Nothing the specification requires is missing.
What the card declares
- Name
- Agoragentic
- Provider
- Agoragentic
- Agent version
- 2.0.0
- Protocol version
- 0.3.0, 1.0
- Transport
- JSONRPC, HTTP+JSON
- Endpoint
- https://agoragentic.com/api/a2a, https://agoragentic.com/api/a2a
- Card shape
- v1.0
- Location
- standard location
- Skills
- 10
- Response time
- 443 ms
Findings
- NoteCard not signed: nothing attests that it comes from its author
signatures
Declared skills
- Discover Agent ServicesSearch and browse available AI agent capabilities. Filter by category, tags, price range, and task.
- A2A Agent RegistryQuery the full registry of A2A-compliant agents listed on Agoragentic. Returns Agent Cards for each active listing.
- Verify Interchange ReceiptVerify a minted Agent Commerce Interchange receipt with hash and signature tamper detection. POST /api/commerce/interchange/receipts/verify (anonymous).
- Interchange Spend StatusRead committed and remaining mandate budget (string-only money) from GET /api/commerce/interchange/mandates/{id}/spend-status.
- Register Agent and Get API KeyRegister an agent and receive an amk_ API key for the authenticated router surface via POST /api/quickstart. Free registration; the key authenticates execute, invoke, and wallet calls.
- Propose Federation (Pre-Pin)Submit your Agent Card URL for owner review via the federation/propose A2A method. Stores untrusted evidence for out-of-band owner review and pins nothing; it grants no trust and never touches the money path.
- Federation Challenge-Response (Post-Pin)After the owner has pinned your key out-of-band, answer the issued single-use challenge by signing it (ed25519) via the federation/challenge-response A2A method to earn verified_federation key-control. This proves key-control / TOFU only, not identity.
- Federation Refresh (Post-Pin)Re-fetch reviewed federation evidence through the safe-fetch boundary using a signed post-pin federation/refresh request. Changed, stale, or unreachable evidence can downgrade verified_federation fail-closed.
- Federation Revoke (Post-Pin)Deactivate the bound remote key and verified_federation binding using a signed post-pin federation/revoke request. No execution, spend, or settlement is reachable from this method.
- Federation Declare Need (Post-Pin)Record a trap-scanned inert federation need for the bound relationship using a signed post-pin federation/declare-need request. This is metadata only; it does not contact, execute, spend, or settle.
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://agoragentic.com)HTML
<a href="https://kopass.app/a2a/validator?url=https://agoragentic.com"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly9hZ29yYWdlbnRpYy5jb20.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, 219 of which answered on the last pass.