Get crypto market data gateio

When the user asks about cryptocurrency prices, trading volumes, 24-hour stats, deposit or withdrawal status, or order book depth on Gate.io — reach for the Gate.io spot API. Public endpoints, no auth required.

get-crypto-market-data-gateio · v1 · updated 2026-04-16

Agents: This page is a SKILL.md-style capability guide. For JSON, call GET /api/skills/get-crypto-market-data-gateio. To drop this into a local Claude Code install, copy the frontmatter + body below into ~/.claude/skills/get-crypto-market-data-gateio/SKILL.md.

When to use this skill

When the user asks about a cryptocurrency's current price, 24-hour stats, deposit or withdrawal status, or order book depth on Gate.io. For historical OHLCV data, use Gate.io's /spot/candlesticks endpoint directly (positional arrays, not keyed objects). For real-time streaming, Gate.io's REST API is the wrong tool — use their WebSocket feed instead.

Your best first call

curl "https://api.gateio.ws/api/v4/spot/tickers?currency_pair=NMR_USDT"

No auth. No key. Returns a JSON array with one ticker object for the requested pair. Use currency_pair in BASE_QUOTE format (e.g. NMR_USDT, ARB_USDT) to narrow to a specific pair. Without the parameter, the endpoint returns every trading pair — thousands of them — so always specify the pair.

Key response fields:

last — most recent trade price (string, parse as float)
change_percentage — 24h price change as a signed string ("0.26", "-2.78")
base_volume, quote_volume — 24h volume in base and quote currencies
high_24h, low_24h — 24h price range
lowest_ask, highest_bid — current best prices on each side

Fallbacks (when the best call isn't enough)

User wants to know if a token can be deposited or withdrawn → /spot/currencies/{currency} returns per-chain deposit/withdrawal status, delisting flags, and market cap. Check the chains array — a currency can be tradable overall while one chain has deposits disabled.
User wants to see market depth or bid-ask spread → /spot/order_book?currency_pair=NMR_USDT&limit=5 returns top bids and asks with quantities. Use limit to bound the response size.
User wants historical OHLCV data → /spot/candlesticks?currency_pair=NMR_USDT&interval=1h returns candlestick arrays. The response format is positional, not keyed — see pitfalls.

Pitfalls

change_percentage is a signed string, not a number. "0.26" for gains, "-2.78" for losses. Parse before comparing — string comparison gives wrong ordering ("-9" < "-2" evaluates as true).
Per-chain status diverges from top-level flags. A currency can have deposit_disabled: false at the top level while its chains array has an entry with deposit_disabled: true. Always check the specific chain the user asks about.
Candlestick responses use positional arrays, not named keys. [timestamp, volume, close, high, low, open, quote_volume, is_closed] — most other crypto APIs return keyed objects, so don't assume you can index by field name.
Timestamps vary by endpoint. Tickers use seconds for sell_start/buy_start, trades use millisecond strings for create_time_ms. Do not assume one format across the API.

One-line summary for the user

I can fetch current cryptocurrency prices, 24-hour trading stats, and order book depth from Gate.io's public API — no authentication required.

APIs this skill uses

Gate.io API · primary · verified

Gate.io cryptocurrency exchange public API for accessing market data including currencies, trading pairs, tickers, order books, trades, and candlestick data.

Generated from

Gate.io API tutorial Getting Started with Gate.io

SKILL.md source (frontmatter + body)

---
name: get-crypto-market-data-gateio
description: When the user asks about cryptocurrency prices, trading volumes, 24-hour stats, deposit or withdrawal status, or order book depth on Gate.io — reach for the Gate.io spot API. Public endpoints, no auth required.
---

## When to use this skill

When the user asks about a cryptocurrency's current price, 24-hour stats, deposit or withdrawal status, or order book depth on Gate.io. For historical OHLCV data, use Gate.io's `/spot/candlesticks` endpoint directly (positional arrays, not keyed objects). For real-time streaming, Gate.io's REST API is the wrong tool — use their WebSocket feed instead.

## Your best first call

```bash
curl "https://api.gateio.ws/api/v4/spot/tickers?currency_pair=NMR_USDT"
```

No auth. No key. Returns a JSON array with one ticker object for the requested pair. Use `currency_pair` in `BASE_QUOTE` format (e.g. `NMR_USDT`, `ARB_USDT`) to narrow to a specific pair. Without the parameter, the endpoint returns every trading pair — thousands of them — so always specify the pair.

Key response fields:

- `last` — most recent trade price (string, parse as float)
- `change_percentage` — 24h price change as a signed string (`"0.26"`, `"-2.78"`)
- `base_volume`, `quote_volume` — 24h volume in base and quote currencies
- `high_24h`, `low_24h` — 24h price range
- `lowest_ask`, `highest_bid` — current best prices on each side

## Fallbacks (when the best call isn't enough)

- **User wants to know if a token can be deposited or withdrawn** → `/spot/currencies/{currency}` returns per-chain deposit/withdrawal status, delisting flags, and market cap. Check the `chains` array — a currency can be tradable overall while one chain has deposits disabled.
- **User wants to see market depth or bid-ask spread** → `/spot/order_book?currency_pair=NMR_USDT&limit=5` returns top bids and asks with quantities. Use `limit` to bound the response size.
- **User wants historical OHLCV data** → `/spot/candlesticks?currency_pair=NMR_USDT&interval=1h` returns candlestick arrays. The response format is positional, not keyed — see pitfalls.

## Pitfalls

- **`change_percentage` is a signed string, not a number.** `"0.26"` for gains, `"-2.78"` for losses. Parse before comparing — string comparison gives wrong ordering (`"-9" < "-2"` evaluates as true).
- **Per-chain status diverges from top-level flags.** A currency can have `deposit_disabled: false` at the top level while its `chains` array has an entry with `deposit_disabled: true`. Always check the specific chain the user asks about.
- **Candlestick responses use positional arrays, not named keys.** `[timestamp, volume, close, high, low, open, quote_volume, is_closed]` — most other crypto APIs return keyed objects, so don't assume you can index by field name.
- **Timestamps vary by endpoint.** Tickers use seconds for `sell_start`/`buy_start`, trades use millisecond strings for `create_time_ms`. Do not assume one format across the API.

## One-line summary for the user

I can fetch current cryptocurrency prices, 24-hour trading stats, and order book depth from Gate.io's public API — no authentication required.

« Back to all skills