ToolVet
77trust / 100

Candles

by Hyperliquid Market Data in Onchain & crypto

x402 APIPassing, checked 3 h ago

OHLCV candles for one Hyperliquid asset over any interval (1m to 1M), normalized into named fields with RFC3339 timestamps.

GET
https://hyperliquid.use.x402atlas.com/candles
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
452 ms
531 ms slowest 5%
Last check
Passed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://hyperliquid.use.x402atlas.com/candles

Each call costs $0.01 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://hyperliquid.use.x402atlas.com/candles?coin=BTC&end=1784332800000&interval=1h&start=1782864000000

Parameters

ParameterTypeRequiredDescription
coinstringYesAsset symbol (e.g. BTC)
endintegerNoOptional end (ms epoch); defaults to now
intervalstringYesCandle interval One of: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 3d.
startintegerNoOptional start (ms epoch); defaults to ~500 intervals ago

Example response

The provider's example. We can't check it without paying.

{
  "candles": [
    {
      "close": "64250.0",
      "close_time": "2026-07-10T12:00:00Z",
      "high": "64300.0",
      "low": "63900.0",
      "open": "64000.0",
      "open_time": "2026-07-10T11:00:00Z",
      "trades": 987,
      "volume": "1234.5"
    }
  ],
  "coin": "BTC",
  "count": 1,
  "interval": "1h",
  "queried_at": "2026-07-10T12:00:00Z"
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://hyperliquid.use.x402atlas.com/candles?coin=BTC&end=1784332800000&interval=1h&start=1782864000000'

# 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://hyperliquid.use.x402atlas.com/candles?coin=BTC&end=1784332800000&interval=1h&start=1782864000000' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhyperliquid.use.x402atlas.com%2Fcandles
const res = await pay("https://hyperliquid.use.x402atlas.com/candles?coin=BTC&end=1784332800000&interval=1h&start=1782864000000");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://hyperliquid.use.x402atlas.com/candles?coin=BTC&end=1784332800000&interval=1h&start=1782864000000")
    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

WhenResultHTTPTimePrice
3 h agoPassed402447 ms$0.01
8 h agoPassed402425 ms$0.01
12 h agoPassed402547 ms$0.01
16 h agoPassed402444 ms$0.01
20 h agoPassed402470 ms$0.01
Show 10 older checks
25 h agoPassed402476 ms$0.01
29 h agoPassed402485 ms$0.01
33 h agoPassed402456 ms$0.01
37 h agoPassed402430 ms$0.01
41 h agoPassed402471 ms$0.01
46 h agoPassed402458 ms$0.01
2 days agoPassed402435 ms$0.01
2 days agoPassed402410 ms$0.01
2 days agoPassed402483 ms$0.01
3 days agoPassed402475 ms$0.01