Paywary

Leaderboard / api.aislabs.ai / endpoint

GET https://api.aislabs.ai/v1/cve/CVE-2026-33824

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 10 probes in the last 7 days.
Category
Other by llm, confidence 35%
Latest quote
$0.005 on Base to 0xeBD2…5AbB
Uptime
100% / 7d, 100% / 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 19:08 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
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0050xeBD2…5AbBdefaultyes16m 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
22h agoOther35%llmv1claude-haiku-5-5: The endpoint returns a CVE priority verdict (score, rank, factors) from a ranked vulnerability set, which is security intelligence. None of the categories cover vulnerability prioritisation directly. The closest fits are signal (risk verdicts) or web_audit, but it does not audit a URL the caller supplies, so 'other' is the safest choice with moderate-low confidence.
44h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
5h agofree40223 msv1yes$0.0050xeBD2…5AbBprotocol_v1
11h agofree402273 msv1yes$0.0050xeBD2…5AbBprotocol_v1
17h agofree402343 msv1yes$0.0050xeBD2…5AbBprotocol_v1
24h agofree402415 msv1yes$0.0050xeBD2…5AbBprotocol_v1
30h agofree40274 msv1yes$0.0050xeBD2…5AbBprotocol_v1
37h agofree402307 msv1yes$0.0050xeBD2…5AbBprotocol_v1
43h agofree402330 msv1yes$0.0050xeBD2…5AbBprotocol_v1
2d agofree40282 msv1yes$0.0050xeBD2…5AbBprotocol_v1
2d agofree402207 msv1yes$0.0050xeBD2…5AbBprotocol_v1
3d agofree402185 msv1yes$0.0050xeBD2…5AbBprotocol_v1