Paywary

Leaderboard / rexvalidate.com / endpoint

POST https://rexvalidate.com/api/agent/v1/litigation

Scores measure reliability and honesty, not output quality.

74Cautionconfidence: medium
  • Answered 8 of 10 probes in the last 7 days (80%).
  • Answered 8 of 10 probes in the last 30 days (80%).
Category
Compliance by llm, confidence 85%
Latest quote
— on — to —
Uptime
80% / 7d, 80% / 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-19 07:37 UTC

Score components

Uptime, 7 days
46w 15%
Uptime, 30 days
46w 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
cdpexactBase0x8335…2913$0.040x362e…37D7defaultyes6h 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
46h agoCompliance85%llmv1claude-haiku-5-5: The endpoint screens phone numbers against TCPA litigator lists to flag or block risky numbers before outreach, which is regulatory and sanctions-style compliance screening rather than lead enrichment or phone validation data.
2d agoEnrichment60%rulesv1rule enrichment matched "lead generation" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
4h agofreenetwork390 ms————no_responsefetch_error:network
11h agofree402255 msv2yes$0.040x362e…37D7—
17h agofree402406 msv2yes$0.040x362e…37D7—
24h agofree402354 msv2yes$0.040x362e…37D7—
30h agofree402397 msv2yes$0.040x362e…37D7—
37h agofree402562 msv2yes$0.040x362e…37D7—
2d agofreetimeout15001 ms————no_responsefetch_error:timeout
2d agofree402224 msv2yes$0.040x362e…37D7—
3d agofree402254 msv2yes$0.040x362e…37D7—
3d agofree402270 msv2yes$0.040x362e…37D7—