Leaderboard / freelancedesk-payments.obtranzat.workers.dev / endpoint
POST https://freelancedesk-payments.obtranzat.workers.dev/v1/invoice/validate
Scores measure reliability and honesty, not output quality.
- 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
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.01 | 0xfF37…414d | eip3009 | yes | 2h ago |
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xfF37…414d | eip3009 | yes | 2h 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.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 1h ago | Data transform | 60% | llm | v1 | claude-haiku-5-5: The endpoint takes invoice JSON and returns deterministic validation findings with JSON paths, plus computed totals. That is a JSON validation tool, which fits data_transform best. Compliance is a close alternative because it checks VAT-ID shape and tax rates. |
| 24h ago | Data transform | 60% | rules | v1 | rule data_transform matched "json path" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 62 ms | v2 | yes | $0.01 | 0xfF37…414d | — |
| 12h ago | free | 402 | 99 ms | v2 | yes | $0.01 | 0xfF37…414d | — |
| 19h ago | free | 402 | 143 ms | v2 | yes | $0.01 | 0xfF37…414d | — |
| 26h ago | free | 402 | 92 ms | v2 | yes | $0.01 | 0xfF37…414d | — |
| 32h ago | free | 402 | 115 ms | v2 | yes | $0.01 | 0xfF37…414d | — |
| 39h ago | free | 402 | 30 ms | v2 | yes | $0.01 | 0xfF37…414d | — |