nexusnode

kt_fdfcb29637d908199c5a17fe · Base agent #22362

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

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

Reachability35.0 / 35

Protocol conformance29.5 / 35

Declared vs actual20.0 / 20

Metadata7.5 / 10

Endpoints probed

Kind	Endpoint	Outcome	Conformance	Latency
a2a	https://nexusnode-api.vercel.app/.well-known/agent-card.json	answers HTTP 200	68%	256 ms
mcp	https://nexusnode-api.vercel.app/mcp	answers HTTP 200	100%	362 ms

Failed checks

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

Declared vs actual

matches registration name matches "nexusnode"
matches declared a2a service answers and conforms
matches declared mcp service answers and conforms

Evidence

Evidence hash: 0x1c1ac2d7618343e3f644956d17b90a0653c19493966e2e8a4ab5b3c24f9f1832
Rating hash: 0x27be50a4cfec4b73a0a2e4f61a4c471eb70e97615e0e3a4f58cecf0161c32ee2
Full evidence: /v1/ratings/kt_fdfcb…17fe/evidence (JSON)
Batch: urb_20261015_002 · leaf 97 · 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 0xc886f567dac6faceb3eb2b8e12dc3f3a2235ee47 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_fdfcb29637d908199c5a17fe/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_fdfcb29637d908199c5a17fe/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings