Leaderboard / allooloo.io / endpoint
GET https://allooloo.io/api
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 10 probes in the last 7 days.
- Category
- Other by llm, confidence 20%
- Latest quote
- $0.01 on Base to 0x0Bfd…0ebB
- 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
- 39m ago
- Next probe
- 2026-11-18 22:35 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x0Bfd…0ebB | default | yes | 6h ago |
| cdp | exact | Base | 0xB200…5344 | $0.01 | 0xF516…C8bF | permit2 | yes | 6h 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 |
|---|---|---|---|---|---|
| 21h ago | Other | 20% | llm | v1 | claude-haiku-5-5: The description is abstract and jargon-heavy: it returns a signed 'statement of record' for a market node, product, or the estate scale block, but never says what data domain that covers. No service name, tags, or example fields are given, so the category is unclear and confidence is low. |
| 44h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 39m ago | free | 402 | 3767 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 7h ago | free | 402 | 90 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 13h ago | free | 402 | 83 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 19h ago | free | 402 | 1322 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 25h ago | free | 402 | 3443 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 32h ago | free | 402 | 99 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 39h ago | free | 402 | 3351 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 46h ago | free | 402 | 75 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 2d ago | free | 402 | 94 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |
| 2d ago | free | 402 | 83 ms | v2 | yes | $0.01 | 0x0Bfd…0ebB | — |