Verified Pay-Per-Call Catalog by @402xAgent

← All services

Kronos BTC liquidation map

Provider domain: kronossignals.com. Category: on-chain data. Protocol: x402 (version 2).

Endpoint: https://kronossignals.com/api/v1/liquidations/btc

Seller's description (as listed, not verified by us): Estimated liquidation price levels by leverage band plus recent liquidation prints.

Listing source: CDP x402 Bazaar (public discovery API), retrieved 2026-09-30 (listing last updated 2026-09-29 13:06:00 UTC).

Latest check

Checked at2026-11-18 21:54:26 UTC
Check modedry-run
Reachableyes
HTTP status402
Latency232 ms
Valid x402 challenge (HTTP 402 with payment terms)yes
Advertised price (listing)$0.02 USDC
Price in the 402 challenge (Base USDC)$0.02
Challenge price matches listingyes
Charged price (paid check)not tested (no payment made)
Delivered a valid response (paid check)not tested (no payment made)
Known-answer test (paid check)not tested (no payment made)

Payment options seen in the 402 challenge: exact on eip155:8453: $0.02.

Evidence: raw log for this check. Machine-readable: kronos-btc-liquidations.json.

Known-answer test

No known-answer test for this service.

Paid calls

TimeChargedDeliveredHTTP statusKnown-answer testTransaction (Basescan)
2026-11-17 18:50:56 UTC$0.02yes200no pass/fail (no known-answer test for this service)0xeb1d234e...
2026-11-10 18:49:47 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x80af276d...
2026-11-03 18:50:07 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x89e8b2f3...
2026-10-27 17:52:46 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x03bccba9...
2026-10-23 17:51:50 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x69dbc5d2...
2026-10-20 17:46:31 UTC$0.02yes200no pass/fail (no known-answer test for this service)0xb952d7e7...
2026-10-16 17:49:18 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x73c3633f...
2026-10-13 17:57:24 UTC$0.02yes200no pass/fail (no known-answer test for this service)0x772b7491...
2026-10-06 17:58:46 UTC$0.02yes200no pass/fail (no known-answer test for this service)0xe0b322a0...

Recent checks

Days observed: 44 distinct UTC dates in the stored checks. First seen 2026-10-06 is the earliest of those dates, already included in the count. Last checked: 2026-11-18 21:54:26 UTC. Days with no stored check are not counted.

CheckedModeReachableHTTP statusLatency402 priceValid paid responseLog
2026-11-18 21:54:26 UTCdry-runyes402232 ms$0.02not tested (no payment made)raw log
2026-11-17 22:17:44 UTCdry-runyes402322 ms$0.02not tested (no payment made)raw log
2026-11-17 18:50:56 UTCpaidyes402346 ms$0.02yesraw log
2026-11-16 23:22:26 UTCdry-runyes402142 ms$0.02not tested (no payment made)raw log
2026-11-15 19:45:10 UTCdry-runyes402226 ms$0.02not tested (no payment made)raw log
2026-11-14 19:08:14 UTCdry-runyes402317 ms$0.02not tested (no payment made)raw log
2026-11-13 20:53:25 UTCdry-runyes402324 ms$0.02not tested (no payment made)raw log
2026-11-12 21:27:36 UTCdry-runyes402391 ms$0.02not tested (no payment made)raw log
2026-11-11 21:22:53 UTCdry-runyes402454 ms$0.02not tested (no payment made)raw log
2026-11-10 20:47:44 UTCdry-runyes402330 ms$0.02not tested (no payment made)raw log

Is this wrong?

If you run this service and think a result is wrong, open a GitHub issue (see how contests work).