Paywary

Leaderboard / apkcube.com / endpoint

GET https://apkcube.com/api/v1/lookup/hash/:hash

Scores measure reliability and honesty, not output quality.

54Cautionconfidence: medium
  • Responded without asking for payment on 7 probes; it may no longer be an x402 endpoint.
  • Answered 7 of 8 probes in the last 7 days (88%).
Category
DNS and domains by llm, confidence 50%
Latest quote
— on — to —
Uptime
88% / 7d, 88% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
5h ago
Next probe
2026-11-18 11:39 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactSolanaEPjFWd…Dt1v50000GXEo7n…4Apjdefaultyes6h ago
cdpexactBase0x8335…2913$0.050xaf4e…9c09defaultyes6h 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
27h agoDNS and domains50%llmv1claude-haiku-5-5: The endpoint takes an MD5, SHA-1 or SHA-256 hash and returns the Android app, version and build it belongs to, which is threat-intel style identification. None of the listed categories is a perfect fit; dns_domain covers threat-intel and IP/domain intelligence most closely, but data_transform or other could also apply, so confidence is moderate.
37h agoData transform60%rulesv1rule data_transform matched "hash" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree40092 ms—no——unexpected_status:400status_not_402
17h agofreenetwork71 ms————no_responsefetch_error:network
24h agofree40055 ms—no——unexpected_status:400status_not_402
30h agofree400149 ms—no——unexpected_status:400status_not_402
36h agofree400171 ms—no——unexpected_status:400status_not_402
42h agofree400138 ms—no——unexpected_status:400status_not_402
2d agofree40066 ms—no——unexpected_status:400status_not_402
2d agofree4003222 ms—no——unexpected_status:400status_not_402