Liquidations BTC
by hyperextend in Markets & finance
Forced-liquidation tape over a time window, reconstructed from the node-fills archive (Hyperliquid has no public liquidations feed). Each row is a trade row (coin, side, px, sz, time, hash, tid, users:[buyer, seller]) plus the liquidation markers (method market|backstop, markPx, liquidatedUser, dir). Priced per asset-hour ($0.005 base, $0.01 HIP-3/HIP-4) plus $0.05 per uncached archive hour pulled; up to 24 asset-hours/request, available ~2h after the hour closes.
https://api.hyperextend.xyz/v1/liquidations/BTC- Price
- $0.111
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 5 h ago, next any minute now
Reliability
Latest check failed 5 h ago: Amount "0.001" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.hyperextend.xyz/v1/liquidations/BTC
Each call costs $0.111 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://api.hyperextend.xyz/v1/liquidations/BTC?end=0&start=0Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
end | integer | No | |
start | integer | No |
Example response
The provider's example. We can't check it without paying.
{
"coin": "BTC",
"dir": "Close Long",
"hash": "0xa2f9738770fb57c6a473043cd486820204b5006d0bfe769846c21eda2fff31b1",
"liquidatedUser": "0xa960b2a0fc5f9f53e99df362052e69980cb57fe4",
"markPx": "41995.0",
"method": "market",
"px": "42000.0",
"side": "A",
"sz": "0.5",
"tid": 859758437920209,
"time": 1700000000123,
"users": [
"0xf513d3489017dea4e04c6a11cc62ec360054d7c6",
"0xa960b2a0fc5f9f53e99df362052e69980cb57fe4"
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.111.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.hyperextend.xyz/v1/liquidations/BTC?end=0&start=0'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.hyperextend.xyz/v1/liquidations/BTC?end=0&start=0' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.111 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.111" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.111 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.hyperextend.xyz%2Fv1%2Fliquidations%2FBTC
const res = await pay("https://api.hyperextend.xyz/v1/liquidations/BTC?end=0&start=0");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.111 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.111"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.hyperextend.xyz/v1/liquidations/BTC?end=0&start=0")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 5 h ago | Amount "0.001" is not in atomic token units | 402 | 133 ms | $0.001 |
| 10 h ago | Amount "0.001" is not in atomic token units | 402 | 519 ms | $0.001 |
| 16 h ago | Amount "0.001" is not in atomic token units | 402 | 364 ms | $0.001 |
| 22 h ago | Amount "0.001" is not in atomic token units | 402 | 114 ms | $0.001 |
| 27 h ago | Amount "0.001" is not in atomic token units | 402 | 351 ms | $0.001 |
Show 10 older checks
| 33 h ago | Amount "0.001" is not in atomic token units | 402 | 113 ms | $0.001 |
| 39 h ago | Amount "0.001" is not in atomic token units | 402 | 182 ms | $0.001 |
| 44 h ago | Amount "0.001" is not in atomic token units | 402 | 354 ms | $0.001 |
| 2 days ago | Amount "0.001" is not in atomic token units | 402 | 339 ms | $0.001 |
| 2 days ago | Amount "0.001" is not in atomic token units | 402 | 36 ms | $0.001 |
| 3 days ago | Amount "0.001" is not in atomic token units | 402 | 107 ms | $0.001 |
| 3 days ago | Amount "0.001" is not in atomic token units | 402 | 491 ms | $0.001 |
| 3 days ago | Amount "0.001" is not in atomic token units | 402 | 111 ms | $0.001 |
| 3 days ago | Amount "0.001" is not in atomic token units | 402 | 489 ms | $0.001 |
| 3 days ago | Amount "0.001" is not in atomic token units | 402 | 171 ms | $0.001 |