VitalityNode

kt_5c820c3c68bd533bb43e0e0e · Base agent #25419

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:52:49 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://nebula-scan-ten.vercel.app/.well-known/agent-card.json	answers HTTP 200	68%	625 ms
mcp	https://nebula-scan-ten.vercel.app/mcp	answers HTTP 200	100%	836 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 "VitalityNode", endpoint says "NebulaScan"
matches declared a2a service answers and conforms
matches declared mcp service answers and conforms

Evidence

Evidence hash: 0x1158e1987673fc2e5044e67823fd00948307770a6be965ca6f187eede0d705e3
Rating hash: 0x405c188f129e0f0e2fa15e40e5a7e4e64a8235b3b03abbf1d9fadbc868f9f807
Full evidence: /v1/ratings/kt_5c820…0e0e/evidence (JSON)
Batch: urb_20261015_003 · leaf 220 · root 0x9d8737ee04…47132e8e · 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 0x98d0af166684b48289f0fca3ad627fe1f109797b 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_5c820c3c68bd533bb43e0e0e/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_5c820c3c68bd533bb43e0e0e/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings