Paywary

Leaderboard / x402-api.heyelsa.ai / endpoint

POST http://x402-api.heyelsa.ai/api/submit_transaction_hash

Scores measure reliability and honesty, not output quality.

88Payconfidence: medium
  • Served over plain HTTP, so payment details can be tampered with in transit.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Other by llm, confidence 10%
Latest quote
$0.005 on Base to 0xEcB6…Ee4D
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
no
First listed
2026-11-16
Last probe
24m ago
Next probe
2026-11-19 00:54 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
100w 15%
Price honesty
100w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
9w 5%
HTTPS
0w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
payaiexactBase0x8335…2913$0.0050xEcB6…Ee4Ddefaultyes2h ago

Paid probes

No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.

Delivery checks

Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.

No delivery checks yet. They run inside the weekly paid probe.

Classification history

Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.

WhenCategoryConfidenceMethodVersionEvidence
14h agoOther10%llmv1claude-haiku-5-5: Endpoint name suggests submitting a blockchain transaction hash, but no description, tags or fields are given to confirm its purpose.
46h agoChain read60%rulesv1rule chain_read matched "transaction hash" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
24m agofree402169 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
8h agofree402153 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
14h agofree402174 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
20h agofree402243 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
27h agofree402167 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
33h agofree4021203 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
40h agofree402161 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
47h agofree402216 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
2d agofree402217 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1
2d agofree402189 msv1yes$0.0050xEcB6…Ee4Dhttp_not_httpsprotocol_v1