Leaderboard / anywaypossible.com / endpoint
POST https://anywaypossible.com/api/payment-guard
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- x402 tooling by llm, confidence 80%
- Latest quote
- $0.01 on Base to 0xe569…5e75
- 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
- 26m ago
- Next probe
- 2026-11-18 05:38 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xe569…5e75 | default | 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 |
|---|---|---|---|---|---|
| 23h ago | x402 tooling | 80% | llm | v1 | claude-haiku-5-5: The endpoint verifies x402 payment challenges before an agent signs, checking the 402 challenge, network, asset, price and recipient. That is x402 payment-header and checker tooling, so x402_meta fits best, though it also has a safety/compliance flavour. |
| 26h ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "402 challenge" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 26m ago | free | 402 | 581 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 7h ago | free | 402 | 845 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 14h ago | free | 402 | 518 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 20h ago | free | 402 | 784 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 26h ago | free | 402 | 582 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 32h ago | free | 402 | 1111 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 38h ago | free | 402 | 266 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |
| 45h ago | free | 402 | 530 ms | v2 | yes | $0.01 | 0xe569…5e75 | — |