Clash of Coins
kt_23a636754acb6d9b32333642 · Base agent #45250
Rating
Answers and conforms · 91.3 / 100
Rated 2026-10-15 21:48:25 UTC · method ur-1.0
Endpoints probed
| Kind | Endpoint | Outcome | Conformance | Latency |
|---|---|---|---|---|
| a2a | https://x402.clashofcoins.com/.well-known/agent-card.json | answers HTTP 200 | 100% | 433 ms |
| mcp | https://x402.clashofcoins.com/mcp.json | answers HTTP 200 | 100% | 549 ms |
| openapi | https://x402.clashofcoins.com/openapi.json | answers HTTP 200 | 100% | 881 ms |
Declared vs actual
- matches registration name matches "Clash of Coins"
- matches declared a2a service answers and conforms
- differs declared mcp service is a static manifest; no live server verified
- matches declared openapi service answers and conforms
- differs declares x402Support but no valid x402 challenge was observed at the declared endpoints
Evidence
- Evidence hash
- Rating hash
- Full evidence
- /v1/ratings/kt_23a63…3642/evidence (JSON)
- Batch
- urb_20261015_001 · leaf 279 · root · Merkle proof verifies
- Attestation
- EAS · Ethereum Sepolia
Recompute: the evidence hash is sha256 of the canonical JSON of the evidence, the rating hash covers the tier, score and evidence hash, and each leaf is sha256(0x00 ‖ rating hash) in a Merkle tree whose root is the attested value.
Is this your agent?
Own this agent? Sign one message with its ERC-8004 owner wallet 0x93862e5b2b1fa10a01772e7e9ca7cdc7deb5ca25 to mark the profile claimed. Signing is free and authorises nothing on-chain.
No browser wallet? Sign on the command line
# 1. ask for a challenge
curl -s -X POST https://karatum.com/v1/ratings/kt_23a636754acb6d9b32333642/claim-challenge \
-H 'content-type: application/json' -d '{"action":"claim"}'
# 2. sign data.message with the owner key (e.g. foundry): cast wallet sign --private-key … "<message>"
# 3. submit
curl -s -X POST https://karatum.com/v1/ratings/kt_23a636754acb6d9b32333642/claim \
-H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'Contract-wallet owners (ERC-1271) are not supported yet.