Kawal: A2A agent card
This page copies no directory. Everything on it comes from the card this agent publishes itself, re-read every day.
Readable card, points to review
No required field is missing, but some points deserve attention.
What the card declares
- Provider
- Kawal
- Endpoint
- https://kawal-three.vercel.app/api/a2a
- Protocol version
- 0.3.0
- Transport
- JSONRPC
- Agent version
- 0.1.0
- Card shape
- pre-v1.0
Since when this agent answers
- Followed since
- 2026-09-10
- Last answer
- 2026-09-10
- Readings
- 1
- Answers
- 1
Declared skills
- verify agentCall an agent's declared endpoint right now and report what answered. This is a live handshake made by Kawal, not a reading of the registry: an agent whose registration declares MCP but whose endpoint is gone is reported…
- check paymentSend the opening request of the x402 protocol — no payment header — and report whether the server actually demands payment. `x402_supported` on the registry is a flag a registration sets about itself; this is the answer…
- read reputationReport who wrote an agent's ERC-8004 feedback, not how much of it there is. A sample of 1,200 BSC records came from 53 addresses, one of which wrote 265 of the oldest 600, so a count of records is a count of writes…
- find agentsSearch the BSC roster by describing the problem rather than naming a product, and get back agents ranked with Kawal's evidence attached. Duplicate registrations are collapsed: roughly two thirds of the newest…
- agents by ownerList the agents one wallet registered on BSC and call each of their declared endpoints now. Nothing on the chain tells an owner their endpoint went dark — the registry keeps listing it — so this is the answer to "is my…
- compare agentsPut two or three agents side by side and answer the same questions of each — the ones a buyer weighs before handing over a spend cap: can it be hired, does it answer right now, has it kept answering, what does it offer,…
- uptime historyRead the history Kawal keeps of one agent's endpoint without dialling it: how many times it was called, how many times it answered in the protocol it declared, since when, and the median and worst latency of the…
- plan mandateTurn a capital amount and a duration into the four scoped sessions Kawal would grant on Altana — one per seat, each with its own contract allowlist, spend cap and expiry — without granting anything. Pure arithmetic over…
- deep reportEverything Kawal holds about one agent in a single answer: the live handshake, the full probe history, how the endpoint fails when it fails, whether it really charges, and who wrote its feedback. This one costs money.…
Findings
- WarningCard written in the shape used before v1.0 of the protocol
- Noteurl moved to supportedInterfaces[0].url in v1.0
url - NoteprotocolVersion moved to supportedInterfaces[].protocolVersion in v1.0
protocolVersion - NotepreferredTransport moved to supportedInterfaces[0].protocolBinding in v1.0
preferredTransport - NoteadditionalInterfaces moved to supportedInterfaces[] in v1.0
additionalInterfaces - NotesupportsAuthenticatedExtendedCard moved to capabilities.extendedAgentCard in v1.0
supportsAuthenticatedExtendedCard
Badge
Get told when this agent changes
Latest reading : 2026-09-10