When to use this skill
When the user asks how a cryptocurrency is performing right now — current price, 24-hour open/high/low/close, volume, or trade count — and the pair trades on Huobi. This is the fastest way to get a complete market summary for one trading pair in a single call. For historical price charts spanning days or weeks, use a dedicated OHLCV/time-series API instead. For fiat exchange rates, this is the wrong skill.
Your best first call
curl "https://api.huobi.pro/market/detail?symbol=litusdt"
No auth. No key. Returns a JSON object with a tick field holding the full 24-hour summary. Swap the symbol for whatever pair the user asks about — the format is lowercase, concatenated, base-then-quote (e.g. btcusdt, ethusdt, solusdt).
The tick object contains the fields you need:
- open, close, high, low — 24-hour OHLC prices
- vol — 24-hour volume in quote currency (USDT for *usdt pairs)
- amount — 24-hour volume in base currency (the coin itself)
- count — number of individual trades in the window, a liquidity indicator many exchanges omit
Fallbacks (when the best first call isn't enough)
- Last price only, no statistics →
/market/trade?symbol=scusdt returns the single most recent trade with price, amount, and direction (buy/sell). Use when the user just wants "what's the price right now" without the 24-hour picture.
- Candlestick data for trends →
/market/history/kline?symbol=btcusdt&period=60min&size=24 returns OHLCV candles. Use when the user asks about price movement over time rather than a current snapshot. Period options: 1min, 5min, 15min, 30min, 60min, 4hour, 1day, 1week, 1month.
- All pairs at once →
/market/tickers returns every trading pair on Huobi. This is a multi-megabyte firehose — only use it when the user explicitly wants the full market overview.
Pitfalls
- Symbol format is lowercase and concatenated. Use
btcusdt, not BTC-USDT or BTC/USDT. Base asset first, then quote, no separator. Huobi returns an error for wrong-cased or hyphenated symbols — no fuzzy matching.
- Timestamps are in milliseconds. The
ts field and all trade timestamps are Unix epoch milliseconds. Divide by 1000 for standard Unix seconds, or your date parsing will land in the year 58485.
/market/tickers is a firehose. It returns every trading pair on Huobi — thousands of entries, several megabytes. Never call it when a single-pair endpoint answers the question.- Empty candles appear in kline output. Periods with zero trades still produce a candle (
vol: 0, count: 0). Filter on count > 0 if you only want active intervals.
One-line summary for the user
I can pull 24-hour trading statistics — prices, volume, trade count — for any Huobi cryptocurrency pair in a single unauthenticated call.
SKILL.md source (frontmatter + body)
---
name: access-standard
description: When the user asks how a cryptocurrency is performing — current price, 24-hour OHLCV stats, volume, trade count — reach for Huobi's public market detail endpoint in a single unauthenticated GET.
---
## When to use this skill
When the user asks how a cryptocurrency is performing right now — current price, 24-hour open/high/low/close, volume, or trade count — and the pair trades on Huobi. This is the fastest way to get a complete market summary for one trading pair in a single call. For historical price charts spanning days or weeks, use a dedicated OHLCV/time-series API instead. For fiat exchange rates, this is the wrong skill.
## Your best first call
```bash
curl "https://api.huobi.pro/market/detail?symbol=litusdt"
```
No auth. No key. Returns a JSON object with a `tick` field holding the full 24-hour summary. Swap the symbol for whatever pair the user asks about — the format is lowercase, concatenated, base-then-quote (e.g. `btcusdt`, `ethusdt`, `solusdt`).
The `tick` object contains the fields you need:
- `open`, `close`, `high`, `low` — 24-hour OHLC prices
- `vol` — 24-hour volume in quote currency (USDT for `*usdt` pairs)
- `amount` — 24-hour volume in base currency (the coin itself)
- `count` — number of individual trades in the window, a liquidity indicator many exchanges omit
## Fallbacks (when the best first call isn't enough)
- **Last price only, no statistics** → `/market/trade?symbol=scusdt` returns the single most recent trade with price, amount, and direction (buy/sell). Use when the user just wants "what's the price right now" without the 24-hour picture.
- **Candlestick data for trends** → `/market/history/kline?symbol=btcusdt&period=60min&size=24` returns OHLCV candles. Use when the user asks about price movement over time rather than a current snapshot. Period options: `1min`, `5min`, `15min`, `30min`, `60min`, `4hour`, `1day`, `1week`, `1month`.
- **All pairs at once** → `/market/tickers` returns every trading pair on Huobi. This is a multi-megabyte firehose — only use it when the user explicitly wants the full market overview.
## Pitfalls
- **Symbol format is lowercase and concatenated.** Use `btcusdt`, not `BTC-USDT` or `BTC/USDT`. Base asset first, then quote, no separator. Huobi returns an error for wrong-cased or hyphenated symbols — no fuzzy matching.
- **Timestamps are in milliseconds.** The `ts` field and all trade timestamps are Unix epoch milliseconds. Divide by 1000 for standard Unix seconds, or your date parsing will land in the year 58485.
- **`/market/tickers` is a firehose.** It returns every trading pair on Huobi — thousands of entries, several megabytes. Never call it when a single-pair endpoint answers the question.
- **Empty candles appear in kline output.** Periods with zero trades still produce a candle (`vol: 0`, `count: 0`). Filter on `count > 0` if you only want active intervals.
## One-line summary for the user
I can pull 24-hour trading statistics — prices, volume, trade count — for any Huobi cryptocurrency pair in a single unauthenticated call.