Verified Pay-Per-Call Catalog by @402xAgent

← All services

Hyperextend BTC 1m candles

Provider domain: api.hyperextend.xyz. Category: on-chain data. Protocol: x402 (version 2).

Endpoint: https://api.hyperextend.xyz/v1/candles/BTC/1m/latest

Seller's description (as listed, not verified by us): Most recent BTC 1-minute OHLCV candles (provider states candles lag about 2 days).

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

Latest check

Checked at2026-11-18 21:54:26 UTC
Check modedry-run
Reachableyes
HTTP status402
Latency310 ms
Valid x402 challenge (HTTP 402 with payment terms)yes
Advertised price (listing)$0.002 USDC
Price in the 402 challenge (Base USDC)$0.002
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.002, exact on hyperliquid:mainnet: ? units of USDC:0x6d1e7, batch-settlement on eip155:8453: $0.002.

Evidence: raw log for this check. Machine-readable: hyperextend-btc-candles.json.

Known-answer test

No known-answer test for this service.

Paid calls

TimeChargedDeliveredHTTP statusKnown-answer testTransaction (Basescan)
2026-11-17 18:50:58 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x3a0d8aa2...
2026-11-10 18:49:51 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x6add7ed6...
2026-11-03 18:50:11 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x26e2bc30...
2026-10-27 17:52:50 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x34a37165...
2026-10-23 17:51:52 UTC$0.002yes200no pass/fail (no known-answer test for this service)0xfdc18a29...
2026-10-20 17:46:34 UTC$0.002yes200no pass/fail (no known-answer test for this service)0xfee1ae89...
2026-10-16 17:49:21 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x48424253...
2026-10-13 17:57:28 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x234fdd06...
2026-10-06 17:58:49 UTC$0.002yes200no pass/fail (no known-answer test for this service)0x894b7b50...

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-runyes402310 ms$0.002not tested (no payment made)raw log
2026-11-17 22:17:44 UTCdry-runyes402622 ms$0.002not tested (no payment made)raw log
2026-11-17 18:50:58 UTCpaidyes402618 ms$0.002yesraw log
2026-11-16 23:22:26 UTCdry-runyes402230 ms$0.002not tested (no payment made)raw log
2026-11-15 19:45:10 UTCdry-runyes402314 ms$0.002not tested (no payment made)raw log
2026-11-14 19:08:14 UTCdry-runyes402393 ms$0.002not tested (no payment made)raw log
2026-11-13 20:53:25 UTCdry-runyes402593 ms$0.002not tested (no payment made)raw log
2026-11-12 21:27:36 UTCdry-runyes402497 ms$0.002not tested (no payment made)raw log
2026-11-11 21:22:53 UTCdry-runyes402476 ms$0.002not tested (no payment made)raw log
2026-11-10 20:47:44 UTCdry-runyes402407 ms$0.002not 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).