Kawal

Name: Kawal
Author: Kawal

AgentA2A

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"kawal-kawal","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability0/4 checks ok

No successful checks in the window.

Endpoints

https://kawal-three.vercel.app/api/a2aa2a · auth: none · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
5 d ago	http head	failed	—	—	disallowed by robots.txt
11 d ago	http head	failed	—	—	disallowed by robots.txt
18 d ago	http head	failed	—	—	disallowed by robots.txt
25 d ago	http head	failed	—	—	disallowed by robots.txt
1 mo ago	http head	failed	—	—	disallowed by robots.txt
1 mo ago	http head	failed	—	—	disallowed by robots.txt
2 mo ago	http head	failed	—	—	disallowed by robots.txt
2 mo ago	http head	failed	—	—	disallowed by robots.txt
2 mo ago	http head	failed	—	—	disallowed by robots.txt
2 mo ago	http head	failed	—	—	disallowed by robots.txt

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. Kawal dials a declared endpoint and reports whether it answered, asks an agent that claims x402 whether it really charges, and reads who wrote its feedback. Nothing here repeats a registry claim without saying so. The same skills are served over MCP at /api/mcp. message/stream narrates a skill as task events and the task is gone once the stream closes; there is no authenticated card, the public one is complete.

erc-8004bnb-chainverification

Declared skills

verify agent — Call 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 as not answering. Returns the hireability tier and the evidence behind it, including how many times Kawal has reached this endpoint before.
check payment — Send 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 to asking. Kawal never settles a payment, so the price is quoted in the server's own words and nothing moves.
read reputation — Report 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 rather than of opinions. Returns how many carry a mark, how many distinct addresses wrote them, and what share came from the busiest one.
find agents — Search 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 registrations are copies of a template, and returning all of them would be returning the same agent many times. With `trending`, the list is instead what 8004scan's visitors looked at most over that window — attention, not evidence — each entry carrying the tier Kawal's own record gives it…
agents by owner — List 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 agent still answering?": what answered, how each failure looks, and every probe Kawal kept. At most 12 agents are dialled, so a large owner sees the first page.
compare agents — Put 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, what does it say it costs, does its domain verify, what is its track record, what is flagged against it, and when it was registered. Each agent is dialled for this call. No combined score: the disagreements are the point.
uptime history — Read 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 answering calls. This is the record the registry does not have. Null when Kawal has never called this endpoint; verify_agent makes the first call.
plan mandate — Turn 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 the venue table: the same plan the mandate form shows, and the same refusals, since a plan that would widen authority (an unproven venue, an empty allowlist, caps that overcommit) is refused rather than built.
deep report — Everything 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. Kawal measured that 75 of 200 BSC registrations declare x402 support and that none of the reachable ones ever asks to be paid; this is the counter-example. Calling it without payment returns the terms rather than the report. Pay the terms with a plain BNB transfer and call again w…

kind A2A Agent Card

name A2A Agent Card

summary A2A Agent Card

version A2A Agent Card

description A2A Agent Card

homepageUrl A2A Agent Card

publisherUrl A2A Agent Card

publisherName A2A Agent Card

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

analytics.reportingReporting & Dashboards89%ai.agent-discoveryAgent Discovery57%commerce.paymentsPayments51%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

A2A Agent Cardhttps://kawal-three.vercel.app/.well-known/agent-card.json

first seen 2 mo ago · fetched 1 mo agoopen ↗

Field history (7 recent events)

2 mo ago · declared · summary → "Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. Kawal dials a declared endpoint and report
2 mo ago · declared · description → "Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. Kawal dials a declared endpoint and report
2 mo ago · declared · publisherName → "Kawal"
2 mo ago · declared · publisherUrl → "https://kawal-three.vercel.app"
2 mo ago · declared · homepageUrl → "https://kawal-three.vercel.app"
2 mo ago · declared · version → "0.1.0"
2 mo ago · declared · protocols → ["a2a"]