Leaderboard / audit.liquidlogicx.com / endpoint
GET https://audit.liquidlogicx.com/api/allowance
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- x402 tooling by llm, confidence 60%
- Latest quote
- $0.001 on Base to 0x1479…8c7b
- 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:40 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0x1479…8c7b | 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 | 60% | llm | v1 | claude-haiku-5-5: The endpoint checks an agent wallet's x402 spend cap and returns whether a payment is allowed, which is payment-policy tooling for x402 agents. It is not a chain read, though it takes a wallet as input and reports USDC figures. x402_meta is the closest fit, with moderate confidence because the category is about x402 tooling generally and the listing describes a policy check rather than a catalog or header tool. |
| 26h ago | Chain read | 60% | rules | v1 | rule chain_read matched "in:wallet" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 26m ago | free | 402 | 504 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 7h ago | free | 402 | 671 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 14h ago | free | 402 | 664 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 20h ago | free | 402 | 631 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 26h ago | free | 402 | 433 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 32h ago | free | 402 | 410 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 38h ago | free | 402 | 394 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |
| 45h ago | free | 402 | 451 ms | v2 | yes | $0.001 | 0x1479…8c7b | — |