Myagent

kt_a7df7cfc384b97528a8fd293 · Base agent #37697

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 · 89.3 / 100

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

Reachability35.0 / 35

Protocol conformance32.2 / 35

Declared vs actual13.3 / 20

Metadata8.8 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://api.helixa.xyz/.well-known/agent-card.json	answers HTTP 200	84%	680 ms
mcp	https://api.helixa.xyz/api/mcp	answers HTTP 200	100%	446 ms

Failed checks

a2a:protocol_declared
a2a:echo_envelope — HTTP 302, not a JSON-RPC 2.0 response

Declared vs actual

differs registration says "Myagent", endpoint says "Helixa"
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: 0x61f3d4ba3ab0c60a2978ee23221fd94d0f40eed36f18e8fc583ed796acc8f75b
Rating hash: 0xab659422cd808eb3161e4986b7e0131c1328b10a338ed5adf9570e9256deaa17
Full evidence: /v1/ratings/kt_a7df7…d293/evidence (JSON)
Batch: urb_20261015_002 · leaf 449 · 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 0x339559a2d1cd15059365fc7bd36b3047bba480e0 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_a7df7cfc384b97528a8fd293/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_a7df7cfc384b97528a8fd293/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings