Endpoint

B

hyperliquid.use.x402atlas.com/candles

Hyperliquid Market Data · score 76/100 · recomputed 28m ago

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

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
76 of 100
recomputed 28m ago

The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.

We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
32m ago 402 518 ms exact
eip155:8453
0x3831…3442 0.010000 clean
7h ago 402 309 ms exact
eip155:8453
0x3831…3442 0.010000 clean
4d ago 402 1033 ms exact
eip155:8453
0x3831…3442 0.010000 clean
4d ago 402 397 ms exact
eip155:8453
0x3831…3442 0.010000 clean

Reference

URLhttps://hyperliquid.use.x402atlas.com/candles
Sourcesbazaar well-known
Recipient per catalogue0x383190a4F26F075Fc2c73F6738eAbf4Dc6F33442
Price per catalogue0.010000
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.