aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Feedback from almost one source
One address wrote most of what is here. That is not proof of anything — a scheduled uptime prober looks exactly like this — but it is one party's opinion rather than a market's, and it is worth knowing which before granting a spend cap.
uptime ×1, 7d ×1Responds, but not as an A2A agent713 ms
0 of 12 checks answered since 2026-08-27Measured from a single vantage point. A missed check means Kawal could not reach it from here, which is not the same as the agent being down.
Two readings8004scan read this endpoint as healthy at 2026-06-07 05:15 UTC. Kawal’s own: 0 of 12 calls answered, the latest did not. The two disagree; 8004scan's reading is a cached check and Kawal's is from 2026-08-31 21:11 UTC, so one of them is out of date.
Kawal called this endpoint at 2026-08-31 21:11:16 UTC · at most a minute old, never from the registry’s cache
Claims x402, asked for nothing
This registration sets the x402 flag. Kawal sent the opening request of the protocol and the server answered without demanding payment, so the flag is unverified here. It may still charge by a route this request cannot see.
Asked at 2026-08-31 21:11:18 UTC · Kawal never settles a payment on a visitor’s behalf
Does not answer
Compare with anotherNo hire stub: a seat is only offered to an agent that answered in its declared protocol.
healthychecked 2026-06-07 05:15
Valid A2A AgentCard (1 skills) (cached)
bitagent.s3.ap-southeast-1.amazonaws.comdomain unverified (HTTP 403)
Domain verification failedmedium
1 service domain could not be verified.
Low quality scoremedium
Total quality score is below 50.
Each bar 0–100, then × weight · scored 2026-08-25