WarpClicker Orchestrator

kt_f34031587854623e3364ac4e · Base agent #51366

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

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

Reachability35.0 / 35

Protocol conformance28.0 / 35

Declared vs actual13.3 / 20

Metadata8.8 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://warpclickerr.vercel.app/.well-known/agent-card.json	answers HTTP 200	60%	353 ms
mcp	https://warpclickerr.vercel.app/api/mcp	answers HTTP 200	100%	845 ms

Failed checks

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

Declared vs actual

differs registration says "WarpClicker Orchestrator", endpoint says "Warp Clicker Orchestrator"
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: 0x91e015e4e78ad29c8914c0f2c0e7aab5393b408d1af42d62ea87e3b062e70013
Rating hash: 0xcc403ea1d3fa1cbed264b3301fd474f5d06740ee9e1aa034a6102d82b093ba84
Full evidence: /v1/ratings/kt_f3403…ac4e/evidence (JSON)
Batch: urb_20261015_001 · leaf 203 · 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_f34031587854623e3364ac4e/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_f34031587854623e3364ac4e/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings