Delx Agent

kt_34429cdaa61844083f720f6c · Base agent #14340

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 · 91.4 / 100
Rated 2026-10-15 21:51:10 UTC · method ur-1.0
Reachability35.0 / 35
Protocol conformance29.8 / 35
Declared vs actual16.7 / 20
Metadata10.0 / 10

Endpoints probed

KindEndpointOutcomeConformanceLatency
a2ahttps://api.delx.ai/.well-known/agent-card.jsonanswers HTTP 200100%777 ms
mcphttps://api.delx.ai/mcpanswers HTTP 20070%1,119 ms
Failed checks
  • mcp:tools_list_ok — HTTP 200

Declared vs actual

  • matches registration name matches "Delx Agent Operations Protocol"
  • 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
0xdc62ddc41cbb2ddf2e73b9f3c99e4bf35f8014c425bdf790d7250c4bbd494966
Rating hash
0x9292131e579f81574c9c769e20e1c63a101f3b10efcdc8163c367130fb2f4696
Full evidence
/v1/ratings/kt_34429…0f6c/evidence (JSON)
Batch
urb_20261015_002 · leaf 239 · 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 0x9f8bd9875b3e0b632a24a3a7c73f7787175e73a2 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_34429cdaa61844083f720f6c/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_34429cdaa61844083f720f6c/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings