YieldMax AI

kt_7d6913cfe3b341a765c141ae · Base agent #26536

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.2 / 100

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

Reachability35.0 / 35

Protocol conformance29.5 / 35

Declared vs actual16.0 / 20

Metadata8.8 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://opsdeck-iota.vercel.app/.well-known/agent-card.json	answers HTTP 200	68%	369 ms
mcp	https://opsdeck-iota.vercel.app/mcp	answers HTTP 200	100%	583 ms

Failed checks

a2a:protocol_declared
a2a:capabilities_object
a2a:skills_have_id_name
a2a:io_modes
a2a:echo_envelope — HTTP 404, not a JSON-RPC 2.0 response

Declared vs actual

differs registration says "YieldMax AI", endpoint says "Opsdeck Control"
matches declared a2a service answers and conforms
matches declared mcp service answers and conforms

Evidence

Evidence hash: 0x18e1401f7a84ab63e1ce9ad1f03fdf504b51c604e40bda5cdb0d6f90b97223d0
Rating hash: 0x0399acc466877184fbd648f08b39511ae74ba28b7974bde54c336c9d3b73966d
Full evidence: /v1/ratings/kt_7d691…41ae/evidence (JSON)
Batch: urb_20261015_002 · leaf 240 · 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 0x9905c35837838131bfc57468fdb78bc8b3bca91d 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_7d6913cfe3b341a765c141ae/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_7d6913cfe3b341a765c141ae/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings