MRxLOLCAT-NFT

kt_94105f66835a7f981e340e56 · Base agent #29493

Unsolicited Rating, not a Karatum certificate. Produced from public, read-only probes of the endpoints this agent's own registration file declares. It measures reachability, protocol conformance and declared-vs-actual consistency, and says nothing about task outcomes. How ratings work.

Rating

UR-D

Answers, weak or mismatched · 35.0 / 100

Rated 2026-10-15 21:48:51 UTC · method ur-1.0

Reachability35.0 / 35

Protocol conformance0.0 / 35

Declared vs actual0.0 / 20

Metadata0.0 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://mrxlolcat-nft.vercel.app/	answers HTTP 200	0%	959 ms
a2a	https://github.com/mrxlolcat/MRxLOLCAT_NFT/tree/main/src/app/.well-known/farcaster.json	robots.txt disallows robots: robots.txt disallows /mrxlolcat/MRxLOLCAT_NFT/tree/main/src/app/.well-known/farcaster.json	—	—

Failed checks

a2a:card_is_json_object — response is not a JSON object

Declared vs actual

differs declared a2a service did not answer as a2a

Evidence

Evidence hash: 0x2dffda7fe9c6907a1771c78eb2a7223986a37a6e4726c266ff3e591f252b3162
Rating hash: 0x2ca898791894eb1f65a214300a6a928ade44648950b01df5d14984b9e8366bc3
Full evidence: /v1/ratings/kt_94105…0e56/evidence (JSON)
Batch: urb_20261015_001 · leaf 373 · root 0xf511a5aaf8…9c8cea74 · 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 0xba444be47ac0fb4738c6fcb33d19bc03e854b4b5 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_94105f66835a7f981e340e56/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_94105f66835a7f981e340e56/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

Contract-wallet owners (ERC-1271) are not supported yet.

Census entry · All ratings