Paywary

Leaderboard / api.crawlwitness.com / endpoint

GET https://api.crawlwitness.com/v1/can-use

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 3 days ago; new listings earn trust over 30 days.
  • Answered all 12 probes in the last 7 days.
Category
Compliance by llm, confidence 80%
Latest quote
$0.001 on Base to 0xa20F…a5C5
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
3h ago
Next probe
2026-11-19 08:22 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
10w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0010xa20F…a5C5defaultyes5h ago
cdpexactSolanaEPjFWd…Dt1v2000DEuats…FFrddefaultyes5h ago
payaiexactBase0x8335…2913$0.0010xa20F…a5C5defaultyes5h ago
payaiexactSolanaEPjFWd…Dt1v2000DEuats…FFrddefaultyes5h 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
2d agoCompliance80%llmv1claude-haiku-5-5: The endpoint returns a yes/no verdict on whether a crawler or RAG pipeline may use a domain for AI, based on robots.txt, AIPREF, TDMRep, noai and RSL licensing signals. That is a regulatory and licensing permission check, which fits compliance best, though it is also close to web_audit or x402-style tooling.
2d agoInference60%rulesv1rule inference matched "rag" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree402604 msv2yes$0.0010xa20F…a5C5—
9h agofree402616 msv2yes$0.0010xa20F…a5C5—
16h agofree402621 msv2yes$0.0010xa20F…a5C5—
23h agofree402628 msv2yes$0.0010xa20F…a5C5—
29h agofree402603 msv2yes$0.0010xa20F…a5C5—
36h agofree402716 msv2yes$0.0010xa20F…a5C5—
42h agofree402671 msv2yes$0.0010xa20F…a5C5—
2d agofree402673 msv2yes$0.0010xa20F…a5C5—
2d agofree402463 msv2yes$0.0010xa20F…a5C5—
3d agofree402638 msv2yes$0.0010xa20F…a5C5—
3d agofree402645 msv2yes$0.0010xa20F…a5C5—
3d agofree402653 msv2yes$0.0010xa20F…a5C5—