Mirror Wars Orchestrator

kt_be0fd754827a585c2053ca17 · Base agent #51334

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

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

Reachability17.5 / 35

Protocol conformance23.3 / 35

Declared vs actual10.0 / 20

Metadata7.5 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://mirror-wars.vercel.app/.well-known/agent-card.json	answers HTTP 200	67%	387 ms
mcp	https://mirror-wars.vercel.app/api/mcp	HTTP error HTTP 404	—	287 ms

Failed checks

a2a:service_url_https — no url / supportedInterfaces[].url
a2a:protocol_declared
a2a:capabilities_object
a2a:io_modes

Declared vs actual

matches registration name matches "Mirror Wars Orchestrator"
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: 0x1ec070549dde7f0c5f9d113252ef53c268f51e2bd0413a56478ccf21bafa0603
Rating hash: 0xa6182589f16227d1969dd10e0c9b66ee3e7cfcf334b1fefca11e301f7bac135a
Full evidence: /v1/ratings/kt_be0fd…ca17/evidence (JSON)
Batch: urb_20261015_001 · leaf 227 · 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_be0fd754827a585c2053ca17/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_be0fd754827a585c2053ca17/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings