Warp Tycoo YGT3 Orchestrator

kt_903e9f66a034cf88ec80a74c · Base agent #51348

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-C

Answers, notable gaps · 65.6 / 100

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

Reachability35.0 / 35

Protocol conformance19.2 / 35

Declared vs actual6.7 / 20

Metadata4.8 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://warp-tycoo-ygt3.vercel.app/.well-known/agent-card.json	answers HTTP 200	67%	495 ms
mcp	https://warp-tycoo-ygt3.vercel.app/api/mcp	answers HTTP 200	43%	863 ms

Failed checks

a2a:service_url_https — no url / supportedInterfaces[].url
a2a:protocol_declared
a2a:capabilities_object
a2a:io_modes
mcp:initialize_protocolVersion
mcp:initialize_serverInfo
mcp:initialize_capabilities

Declared vs actual

differs registration says "Warp Tycoo YGT3 Orchestrator", endpoint says "Cast Spell Wizard Duels Agent"
matches declared a2a service answers and conforms
differs declared mcp service did not answer as mcp
differs declares x402Support but no valid x402 challenge was observed at the declared endpoints

Evidence

Evidence hash: 0xf9f5cc1ea047f3f22421a55156dc025e8dc183c25c57d930836ab37c2b6a20ca
Rating hash: 0xf47951290e01a0a3f1300e3ef9cfbc5a2acedc639a7626c4dcab225957c8ac3e
Full evidence: /v1/ratings/kt_903e9…a74c/evidence (JSON)
Batch: urb_20261015_001 · leaf 213 · 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 0x29536d0bc1004ab274c4f0f59734ad74d4559b7b 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_903e9f66a034cf88ec80a74c/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_903e9f66a034cf88ec80a74c/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings