Paywary

Leaderboard / dt0ur.online / endpoint

POST https://dt0ur.online/api/documents/parse

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
Document by llm, confidence 80%
Latest quote
$0.01 on Base to 0x7f52…89b7
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-18 19:07 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
8w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactSolanaEPjFWd…Dt1v100006PSaCV…GsQXdefaultyes3h ago
cdpexactBase0x8335…2913$0.010x7f52…89b7defaultyes3h 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
24h agoDocument80%llmv1claude-haiku-5-5: The endpoint parses EDI documents (ANSI X12, UN/EDIFACT) into structured JSON, CSV, cXML, or a rendered PDF invoice, which is document conversion and parsing, so the document category fits best, though EDI-specific business data could arguably suggest data_transform.
41h agox402 tooling60%rulesv1rule x402_meta matched "402 challenge" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
1h agofree40282 msv2yes$0.010x7f52…89b7—
7h agofree40285 msv2yes$0.010x7f52…89b7—
14h agofree402772 msv2yes$0.010x7f52…89b7—
20h agofree402741 msv2yes$0.010x7f52…89b7—
27h agofree402826 msv2yes$0.010x7f52…89b7—
33h agofree402118 msv2yes$0.010x7f52…89b7—
39h agofree402104 msv2yes$0.010x7f52…89b7—
45h agofree40298 msv2yes$0.010x7f52…89b7—
2d agofree40276 msv2yes$0.010x7f52…89b7—
2d agofree40265 msv2yes$0.010x7f52…89b7—