Karatumbrick.blue
kt_9b1a645961be1fcdd0ad5ac4 · Base agent #99184
Rating
Answers and conforms · 100.0 / 100
Rated 2026-10-15 21:43:23 UTC · method ur-1.0
Endpoints probed
| Kind | Endpoint | Outcome | Conformance | Latency |
|---|---|---|---|---|
| a2a | https://brick.blue/.well-known/agent-card.json | answers HTTP 200 | 100% | 1,269 ms |
| mcp | https://brick.blue/mcp | answers HTTP 200 | 100% | 1,225 ms |
| x402 | https://brick.blue/.well-known/x402 | answers HTTP 200 | 100% | 5,888 ms |
Declared vs actual
- matches registration name matches "brick.blue"
- matches declared a2a service answers and conforms
- matches declared mcp service answers and conforms
- matches declared x402 service answers and conforms
- matches a valid x402 payment challenge was observed
Evidence
- Evidence hash
- Rating hash
- Full evidence
- /v1/ratings/kt_9b1a6…5ac4/evidence (JSON)
- Batch
- urb_20261015_001 · leaf 17 · 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 0x8e5b627b6b19d45623cc4a47f32ea588e158d405 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_9b1a645961be1fcdd0ad5ac4/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_9b1a645961be1fcdd0ad5ac4/claim \
-H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'Contract-wallet owners (ERC-1271) are not supported yet.