Paywary

Leaderboard / x402.deepsense.stream / endpoint

POST http://x402.deepsense.stream/api/v1/feedback

Scores measure reliability and honesty, not output quality.

62Cautionconfidence: medium
  • Responded without asking for payment on 9 probes; it may no longer be an x402 endpoint.
  • Served over plain HTTP, so payment details can be tampered with in transit.
Category
Commerce by llm, confidence 35%
Latest quote
— on — to —
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
6h ago
Next probe
2026-11-18 16:07 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
payaiexactBase0x8335…2913$0.0020xD1E7…cFd5defaultyes5h 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
17h agoCommerce35%llmv1claude-haiku-5-5: The endpoint collects paid feedback and capability requests from users rather than returning data or tool output, so it fits nothing precisely. Commerce is the closest fit as a paid submission/intake service, but the listing is vague about what the caller receives, so confidence is low.
42h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
6h agofree201518 ms—no——http_not_httpsno_payment_requiredstatus_not_402
12h agofree201501 ms—no——http_not_httpsno_payment_requiredstatus_not_402
18h agofree201600 ms—no——http_not_httpsno_payment_requiredstatus_not_402
24h agofree201829 ms—no——http_not_httpsno_payment_requiredstatus_not_402
31h agofree201579 ms—no——http_not_httpsno_payment_requiredstatus_not_402
37h agofree201621 ms—no——http_not_httpsno_payment_requiredstatus_not_402
44h agofree201524 ms—no——http_not_httpsno_payment_requiredstatus_not_402
2d agofree2011096 ms—no——http_not_httpsno_payment_requiredstatus_not_402
2d agofree201507 ms—no——http_not_httpsno_payment_requiredstatus_not_402