Paywary

Leaderboard / predator-ubuntu.taild9a745.ts.net / endpoint

POST https://predator-ubuntu.taild9a745.ts.net/v1/batch

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 10 probes in the last 7 days.
Category
Utility by llm, confidence 35%
Latest quote
$0.02 on Base to 0x8366…844E
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
4h ago
Next probe
2026-11-18 22:32 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
9w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.020x8366…844Edefaultyes3h ago

Listing changes

WhenEventFromTo
9h agoreappearedfalsetrue
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
9h agoUtility35%llmv1claude-haiku-5-5: Description says it runs multiple utils operations in one call, but the underlying operations are unspecified, so it is a generic batch wrapper.
9h agoOther40%rulesv1rule none matched "" in none
24h agoOther10%llmv1claude-haiku-5-5: The listing has no service name, tags, description, or example inputs. The path /v1/batch hints at a generic batched request endpoint but does not reveal what it returns, so the category cannot be determined with any real confidence.
47h agoOther20%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofree402580 msv2yes$0.020x8366…844E—
10h agofree402683 msv2yes$0.020x8366…844E—
16h agofree402721 msv2yes$0.020x8366…844E—
22h agofree4021117 msv2yes$0.020x8366…844E—
28h agofree402692 msv2yes$0.020x8366…844E—
35h agofree4024260 msv2yes$0.020x8366…844E—
42h agofree4021353 msv2yes$0.020x8366…844E—
2d agofree402733 msv2yes$0.020x8366…844E—
2d agofree402713 msv2yes$0.020x8366…844E—
3d agofree402596 msv2yes$0.020x8366…844E—