Paywary

Leaderboard / twit-api-production-de12.up.railway.app / endpoint

GET https://twit-api-production-de12.up.railway.app/users/following

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 3 days ago; new listings earn trust over 30 days.
  • Answered all 11 probes in the last 7 days.
Category
Web scrape by llm, confidence 35%
Latest quote
$0.01 on Base to 0x9dBA…0df8
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
33m ago
Next probe
2026-11-19 13:15 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
11w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
payaiexactBase0x8335…2913$0.010x9dBA…0df8defaultyes1h 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
27h agoWeb scrape35%llmv1claude-haiku-5-5: Host name suggests Twitter/X API returning user following lists, but no description; likely social media data, closest fit is web_scrape or search-like retrieval.
2d agoOther20%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
33m agofree402210 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
7h agofree402197 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
13h agofree402174 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
20h agofree402155 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
26h agofree402230 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
33h agofree402170 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
39h agofree402213 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
46h agofree402199 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
2d agofree402209 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
2d agofree402222 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
3d agofree402205 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch
3d agofree402156 msv2yes$0.010x9dBA…0df8resource_url_host_mismatch