Paywary

Leaderboard / proxy.suverse.io / endpoint

POST https://proxy.suverse.io/v1/data/suverse-pypi-package

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
Other by llm, confidence 10%
Latest quote
$0.05 on Base to 0xe903…b751
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
1h ago
Next probe
2026-11-19 08:42 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

Listing changes

WhenEventFromTo
29h agodisappeared——
29h agodisappeared——
29h 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
29h agoOther10%llmv1claude-haiku-5-5: The listing has no description, tags, or service name, and the resource path suggests a PyPI package dataset but gives too little to classify confidently.
29h agoPublic data50%rulesv1rule public_data matched "pypi" in metadata
32h agoPublic data50%llmv1claude-haiku-5-5: Returns PyPI package metadata (version, author, license, release files). This is open software registry data, which doesn't cleanly match web_search or web_scrape; public_data is the closest open-dataset fit, though a developer-tools or other category could also be argued and the listing is somewhat sparse on tags.
2d agoPublic data60%rulesv1rule public_data matched "pypi" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
1h agofree402186 msv2yes$0.050xe903…b751—
8h agofree402196 msv2yes$0.050xe903…b751—
15h agofree402519 msv2yes$0.050xe903…b751—
21h agofree402185 msv2yes$0.050xe903…b751—
27h agofree402482 msv2yes$0.050xe903…b751—
33h agofree402654 msv2yes$0.050xe903…b751—
40h agofree402529 msv2yes$0.050xe903…b751—
46h agofree402519 msv2yes$0.050xe903…b751—
2d agofree402710 msv2yes$0.050xe903…b751—
2d agofree402186 msv2yes$0.050xe903…b751—
3d agofree402625 msv2yes$0.050xe903…b751—
3d agofree402169 msv2yes$0.050xe903…b751—