Leaderboard / data.kagurazaka.dev / endpoint
GET https://data.kagurazaka.dev/v1/spend
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Chain read by llm, confidence 60%
- Latest quote
- $0.005 on Base to 0xF164…f8a5
- 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
- 4h ago
- Next probe
- 2026-11-19 01:50 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0xF164…f8a5 | default | 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 |
|---|---|---|---|---|---|
| 46h ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint reads on-chain USDC transfers on Base to report a wallet's x402 spending, totals, per-seller and per-day breakdowns, and recent payments. That is public chain data, though it is framed as analytics over x402 payments, so it could also fit x402_meta; chain_read is the closest match for what it returns. |
| 2d ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "bazaar" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 242 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 11h ago | free | 402 | 319 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 17h ago | free | 402 | 236 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 23h ago | free | 402 | 209 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 30h ago | free | 402 | 290 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 37h ago | free | 402 | 257 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 43h ago | free | 402 | 280 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 2d ago | free | 402 | 254 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 2d ago | free | 402 | 245 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 3d ago | free | 402 | 246 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |
| 3d ago | free | 402 | 312 ms | v2 | yes | $0.005 | 0xF164…f8a5 | — |