Paywary

Leaderboard / dorothy-x402.onrender.com / endpoint

POST https://dorothy-x402.onrender.com/base/tx-preflight

Scores measure reliability and honesty, not output quality.

79Payconfidence: medium
  • 9 probes got a response that was not a 402 payment challenge.
  • Listed only 2 days ago; new listings earn trust over 30 days.
Category
Other by llm, confidence 15%
Latest quote
— on — to —
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
2h ago
Next probe
2026-11-19 05:02 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
18w 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

Listing changes

WhenEventFromTo
2d agodisappeared——

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
28h agoOther15%llmv1claude-haiku-5-5: The listing has no service name, description, tags, or example fields. The path '/base/tx-preflight' hints at a Base chain transaction check, possibly a simulation or pre-flight validation, but the endpoint's actual output cannot be determined from the listing, so the category is a low-confidence guess left as other.
2d agoChain read60%rulesv1rule chain_read matched "/base/" in metadata

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree400145 ms—no——unexpected_status:400status_not_402
8h agofree400185 ms—no——unexpected_status:400status_not_402
14h agofree400118 ms—no——unexpected_status:400status_not_402
21h agofree400114 ms—no——unexpected_status:400status_not_402
27h agofree400109 ms—no——unexpected_status:400status_not_402
33h agofree400128 ms—no——unexpected_status:400status_not_402
40h agofree40049 ms—no——unexpected_status:400status_not_402
46h agofree400145 ms—no——unexpected_status:400status_not_402
2d agofree400104 ms—no——unexpected_status:400status_not_402
2d agofree402126 msv2yes$0.10xDF10…9aF8—
3d agofree40246 msv2yes$0.10xDF10…9aF8—