AbaPay

kt_9d0031243e1274b328d71cc1 · Base agent #59561

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-B
Answers, minor gaps · 71.1 / 100
Rated 2026-10-15 21:46:49 UTC · method ur-1.0
Reachability17.5 / 35
Protocol conformance35.0 / 35
Declared vs actual8.6 / 20
Metadata10.0 / 10

Endpoints probed

KindEndpointOutcomeConformanceLatency
mcphttps://agents.abapays.com/api/mcpanswers HTTP 200100%757 ms
x402https://agents.abapays.com/api/pay/x402unreachable
network: Parse Error: Header overflow
——

Declared vs actual

  • matches registration name matches "abapay"
  • matches declared mcp service answers and conforms
  • differs declared x402 service did not answer as x402
  • differs 0 of 8 declared skills appear in what the endpoint exposes
  • differs declares x402Support but no valid x402 challenge was observed at the declared endpoints

Evidence

Evidence hash
0xa9bbc0a32dcfee1b8e5a89254f7b5232301a2e3080b802efec8854d10fcfab5f
Rating hash
0x70ff0d8d7980f4ceb58d7bc2691923b5834dfd257bc50e53eae3ad673706d0d6
Full evidence
/v1/ratings/kt_9d003…1cc1/evidence (JSON)
Batch
urb_20261015_001 · leaf 82 · 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 0xec24bafbc989a9be5f6f0ead8848753b5e4ae0b6 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_9d0031243e1274b328d71cc1/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_9d0031243e1274b328d71cc1/claim \
  -H 'content-type: application/json' -d '{"nonce":"<nonce>","signature":"0x…"}'

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

Census entry · All ratings