Paywary

Leaderboard / freelancedesk-payments.obtranzat.workers.dev / endpoint

POST https://freelancedesk-payments.obtranzat.workers.dev/v1/invoice/preflight

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 6 probes in the last 7 days.
Category
Data transform by llm, confidence 60%
Latest quote
$0.01 on Base to 0xfF37…414d
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-16
Last probe
6h ago
Next probe
2026-11-17 21:39 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
payaiexactBase0x8335…2913$0.010xfF37…414deip3009yes2h ago
cdpexactBase0x8335…2913$0.010xfF37…414deip3009yes2h 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
1h agoData transform60%llmv1claude-haiku-5-5: The endpoint validates invoice JSON and computes net, tax and total, returning blocking errors. It is a deterministic JSON validation and calculation tool, which fits data_transform best, though compliance (tax) and utility (calculator) were considered. Confidence is moderate because the invoicing domain is ambiguous across several categories.
24h agoData transform60%rulesv1rule data_transform matched "json path" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
6h agofree402139 msv2yes$0.010xfF37…414d—
13h agofree402107 msv2yes$0.010xfF37…414d—
19h agofree402145 msv2yes$0.010xfF37…414d—
26h agofree40294 msv2yes$0.010xfF37…414d—
33h agofree40255 msv2yes$0.010xfF37…414d—
39h agofree40210 msv2yes$0.010xfF37…414d—