Limitguard Lead Verification

kt_068d62249f5fb96d08ee2122 · Base agent #95545

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-A
Answers and conforms · 94.6 / 100
Rated 2026-10-15 21:46:11 UTC · method ur-1.0
Reachability35.0 / 35
Protocol conformance32.9 / 35
Declared vs actual16.7 / 20
Metadata10.0 / 10

Endpoints probed

KindEndpointOutcomeConformanceLatency
a2ahttps://api.limitguard.ai/.well-known/agent-card.jsonanswers HTTP 20088%666 ms
mcphttps://api.limitguard.ai/mcpanswers HTTP 200100%1,487 ms
Failed checks
  • a2a:card_service_url_answers — timeout

Declared vs actual

  • matches registration name matches "Limitguard"
  • matches declared a2a service answers and conforms
  • matches declared mcp service answers and conforms
  • differs declares x402Support but no valid x402 challenge was observed at the declared endpoints

Evidence

Evidence hash
0xf8220ae310b1274f66c292859df270e8b839bce1d4a3fd9c5ed1ec1ea3361a65
Rating hash
0xa11d61d04bbba0a67da914198850a22d15f473380f1a95bb55d6b39549067ffc
Full evidence
/v1/ratings/kt_068d6…2122/evidence (JSON)
Batch
urb_20261015_001 · leaf 47 · 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 0x8a4b64e5615b380b9faeef49764dcfcdc1b637c6 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_068d62249f5fb96d08ee2122/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_068d62249f5fb96d08ee2122/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings