Leaderboard / api.agentweather.io / endpoint
GET https://api.agentweather.io/v1/agent-weather/current
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 6 probes in the last 7 days.
- Category
- Other by llm, confidence 35%
- Latest quote
- $0.007 on Base to 0xA15c…F4Ec
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 6h ago
- Next probe
- 2026-11-17 16:50 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.007 | 0xA15c…F4Ec | default | yes | 3h ago |
| cdp | exact | xrpl:0 | 524C55…0000 | — | rnFHPG…jrZZ | default | yes | 3h ago |
| cdp | exact | Base | 0x8d58…8258 | $7000000000 | 0xA15c…F4Ec | permit2 | 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. Delivery results do not affect scores yet.
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 |
|---|---|---|---|---|---|
| 16h ago | Other | 35% | llm | v1 | claude-haiku-5-5: The service is named Agent Weather but the description is a combined status feed covering AI provider health, XRPL x402 payment readings, and GitHub/npm/MCP Registry readings. It does not fit cleanly into a single category; it is closest to a status/monitoring aggregator, which no category covers well, so 'other' is the best fit with modest confidence. |
| 19h ago | Utility | 60% | rules | v1 | rule utility matched "weather" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 139 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |
| 12h ago | free | 402 | 191 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |
| 19h ago | free | 402 | 468 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |
| 25h ago | free | 402 | 136 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |
| 31h ago | free | 402 | 176 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |
| 38h ago | free | 402 | 140 ms | v2 | option ok | $0.007 | 0xA15c…F4Ec | malformed_challenge accepts[1].amount_not_uint_string |