Paywary

Leaderboard / twitter.surf.cascade.fyi / endpoint

POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/following

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 7 probes in the last 7 days.
Category
Web scrape by llm, confidence 60%
Latest quote
$0.004 on Base to 0xC751…86A1
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-16
Last probe
3h ago
Next probe
2026-11-17 23:21 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
6w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen

Listing changes

WhenEventFromTo
14h agodisappeared——
14h agodisappeared——
14h 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
13h agoWeb scrape60%llmv1claude-haiku-5-5: The host and path suggest it returns a Twitter/X user's following list, which is social media profile data fetched from the web. No description or tags are given, so confidence is moderate. It could also be classed as web_search since it is social media data, but web_scrape fits a profile-fetch style endpoint better.
13h agoOther20%rulesv1rule none matched "" in none
23h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree402518 msv2yes$0.0040xC751…86A1—
10h agofree402517 msv2yes$0.0040xC751…86A1—
16h agofree402169 msv2yes$0.0040xC751…86A1—
22h agofree402492 msv2yes$0.0040xC751…86A1—
28h agofree402534 msv2yes$0.0040xC751…86A1—
35h agofree402165 msv2yes$0.0040xC751…86A1—
41h agofree402160 msv2yes$0.0040xC751…86A1—