Leaderboard / changelog-state-api.replit.app / endpoint
GET https://changelog-state-api.replit.app/api/monitors/chainlink/changes
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Other by llm, confidence 35%
- Latest quote
- $0.01 on Base to 0xb23c…6fc9
- 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
- 3h ago
- Next probe
- 2026-11-18 04:06 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.01 | 0xb23c…6fc9 | default | yes | 2h ago |
| payai | exact | Solana | EPjFWd…Dt1v | 10000 | 6UNbfD…4yct | 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 |
|---|---|---|---|---|---|
| 5h ago | Other | 35% | llm | v1 | claude-haiku-5-5: The listing describes detected changelog update history for a tracked vendor, which does not map cleanly to any category. It is closest to web monitoring, but no existing category covers vendor changelog tracking, and the description is brief with no tags. |
| 27h ago | Public data | 60% | rules | v1 | rule public_data matched "changelog" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 222 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 9h ago | free | 402 | 253 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 16h ago | free | 402 | 647 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 22h ago | free | 402 | 313 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 30h ago | free | 402 | 324 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 36h ago | free | 402 | 332 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |
| 42h ago | free | 402 | 299 ms | v2 | yes | $0.01 | 0xb23c…6fc9 | — |