Leaderboard / verify.agentutil.net / endpoint
POST https://verify.agentutil.net/v1/verify
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 11 probes; it may no longer be an x402 endpoint.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Category
- Other by llm, confidence 35%
- Latest quote
- — on — to —
- 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-19 01:29 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.004 | 0x1357…142d | default | yes | 3h 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 |
|---|---|---|---|---|---|
| 44h ago | Other | 35% | llm | v1 | claude-haiku-5-5: Fact verification returning verdict and confidence could be inference-based checking or a signal-like verdict, but the listing is brief with no service name or tags and does not clearly map to a single category. The 'current truth' wording suggests a web-grounded claim check, which sits closest to inference, so the classification is low confidence. |
| 47h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 1h ago | free | 200 | 1278 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 8h ago | free | 200 | 1079 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 15h ago | free | 200 | 1009 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 21h ago | free | 200 | 1576 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 28h ago | free | 200 | 1350 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 34h ago | free | 200 | 1035 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 40h ago | free | 200 | 1568 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 46h ago | free | 200 | 1543 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 2d ago | free | 200 | 1216 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 2d ago | free | 200 | 878 ms | — | no | — | — | no_payment_requiredstatus_not_402 |
| 3d ago | free | 200 | 1459 ms | — | no | — | — | no_payment_requiredstatus_not_402 |