Loopuman

kt_4bf042cfa9295c9cffb5bea4 · Base agent #24044

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-B
Answers, minor gaps · 82.3 / 100
Rated 2026-10-15 21:49:16 UTC · method ur-1.0
Reachability31.5 / 35
Protocol conformance31.3 / 35
Declared vs actual12.0 / 20
Metadata7.5 / 10

Endpoints probed

KindEndpointOutcomeConformanceLatency
a2ahttps://api.loopuman.com/.well-known/agent-card.jsonanswers HTTP 20079%1,600 ms
mcphttps://api.loopuman.com/.well-known/mcp.jsonanswers HTTP 200100%1,599 ms
Failed checks
  • a2a:protocol_declared
  • a2a:io_modes
  • a2a:echo_envelope — HTTP 404, not a JSON-RPC 2.0 response

Declared vs actual

  • matches registration name matches "Loopuman"
  • matches declared a2a service answers and conforms
  • differs declared mcp service is a static manifest; no live server verified

Evidence

Evidence hash
0x3d47230670292b4d5384561d708e6f6d2dc54085938106693f02ef1bf21e349c
Rating hash
0x1e3d3c867193a39465f5c016089969e7ded9445a0510c764ea4461fd8248509c
Full evidence
/v1/ratings/kt_4bf04…bea4/evidence (JSON)
Batch
urb_20261015_002 · leaf 3 · root 0xa8bc5c7d37…51d649cd · 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 0xef4acd50101c2afd14c2c213b30d8d8e9a91f0d2 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_4bf042cfa9295c9cffb5bea4/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_4bf042cfa9295c9cffb5bea4/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings