When to use this skill
When the user asks about a cryptocurrency's current price, 24-hour stats, bid-ask spread, or trading-pair configuration on NovaDAX — a Brazilian exchange where nearly all 580+ pairs are denominated in BRL, not USDT. This is the right skill when the question involves reais or BRL-denominated crypto pricing specifically. For USD or USDT-denominated prices, use Binance or CoinGecko instead. For historical candlestick data, this is the wrong skill.
Your best first call
curl "https://api.novadax.com/v1/market/ticker?symbol=SOL_BRL"
No auth. No key. Returns a JSON object with 24-hour rolling data for one pair. The symbol parameter uses BASE_QUOTE format — all BRL pairs end in _BRL, USDT pairs in _USDT.
Key fields in the data object:
lastPrice — most recent trade price (e.g. "421.009" BRL for SOL)high24h, low24h, open24h — 24-hour range; open24h vs lastPrice gives the daily movebid, ask — current best bid and ask; the gap between them is the spread, which on BRL pairs is characteristically widebaseVolume24h, quoteVolume24h — 24-hour volume in base and quote currenciestimestamp — millisecond epoch (divide by 1000 for most date libraries)
Fallbacks (when the best call isn't enough)
- Order book depth for a pair →
/v1/market/depth?symbol=BTC_USDT&limit=5 returns top bids and asks as [price, quantity] arrays. Use when the user asks about liquidity, spread detail, or "how deep is the book".
- Trading rules and minimums for a pair →
/v1/common/symbol?symbol=BTC_USDT returns amountPrecision, pricePrecision, minOrderAmount, and minOrderValue. Use before placing orders — the exchange rejects anything below minimums. BRL pairs typically require 25 BRL minimum notional.
- All tickers at once →
/v1/market/tickers returns 595+ objects in one call (~130 KB). Only use when the user explicitly wants every pair listed.
Pitfalls
- BRL spreads are wide. The bid-ask gap on SOL_BRL (~2.5%) is roughly 50x wider than on SOL_USDT on Binance. Report spreads with context or the user will think something is broken.
/v1/market/tickers is a 130 KB+ firehose. Always use /v1/market/ticker?symbol=XYZ for a single pair. The plural endpoint will flood the context window.- Timestamps are milliseconds, not seconds. The
timestamp field is a 13-digit epoch. Divide by 1000 before passing to most date libraries.
/v1/market/kline/history rejects MIN. Use MINUTE, HOUR, or DAY for the unit parameter — the server-side Java enum does not accept abbreviations.
One-line summary for the user
I can get real-time crypto prices, order books, and trading-pair details from NovaDAX — a Brazilian exchange where pairs are priced in BRL, with no auth required for public data.
NovaDAX cryptocurrency exchange API providing market data including tickers, order books, trades, and symbol information. Public endpoints do not require authentication.
SKILL.md source (frontmatter + body)
---
name: access-real-time
description: When the user asks about a cryptocurrency's current price, bid-ask spread, 24-hour stats, or trading-pair rules on NovaDAX — a Brazilian exchange where pairs are priced in BRL — reach for the NovaDAX public market API. No auth required.
---
## When to use this skill
When the user asks about a cryptocurrency's current price, 24-hour stats, bid-ask spread, or trading-pair configuration on NovaDAX — a Brazilian exchange where nearly all 580+ pairs are denominated in BRL, not USDT. This is the right skill when the question involves reais or BRL-denominated crypto pricing specifically. For USD or USDT-denominated prices, use Binance or CoinGecko instead. For historical candlestick data, this is the wrong skill.
## Your best first call
```bash
curl "https://api.novadax.com/v1/market/ticker?symbol=SOL_BRL"
```
No auth. No key. Returns a JSON object with 24-hour rolling data for one pair. The `symbol` parameter uses `BASE_QUOTE` format — all BRL pairs end in `_BRL`, USDT pairs in `_USDT`.
Key fields in the `data` object:
- `lastPrice` — most recent trade price (e.g. "421.009" BRL for SOL)
- `high24h`, `low24h`, `open24h` — 24-hour range; `open24h` vs `lastPrice` gives the daily move
- `bid`, `ask` — current best bid and ask; the gap between them is the spread, which on BRL pairs is characteristically wide
- `baseVolume24h`, `quoteVolume24h` — 24-hour volume in base and quote currencies
- `timestamp` — millisecond epoch (divide by 1000 for most date libraries)
## Fallbacks (when the best call isn't enough)
- **Order book depth for a pair** → `/v1/market/depth?symbol=BTC_USDT&limit=5` returns top bids and asks as `[price, quantity]` arrays. Use when the user asks about liquidity, spread detail, or "how deep is the book".
- **Trading rules and minimums for a pair** → `/v1/common/symbol?symbol=BTC_USDT` returns `amountPrecision`, `pricePrecision`, `minOrderAmount`, and `minOrderValue`. Use before placing orders — the exchange rejects anything below minimums. BRL pairs typically require 25 BRL minimum notional.
- **All tickers at once** → `/v1/market/tickers` returns 595+ objects in one call (~130 KB). Only use when the user explicitly wants every pair listed.
## Pitfalls
- **BRL spreads are wide.** The bid-ask gap on SOL_BRL (~2.5%) is roughly 50x wider than on SOL_USDT on Binance. Report spreads with context or the user will think something is broken.
- **`/v1/market/tickers` is a 130 KB+ firehose.** Always use `/v1/market/ticker?symbol=XYZ` for a single pair. The plural endpoint will flood the context window.
- **Timestamps are milliseconds, not seconds.** The `timestamp` field is a 13-digit epoch. Divide by 1000 before passing to most date libraries.
- **`/v1/market/kline/history` rejects `MIN`.** Use `MINUTE`, `HOUR`, or `DAY` for the `unit` parameter — the server-side Java enum does not accept abbreviations.
## One-line summary for the user
I can get real-time crypto prices, order books, and trading-pair details from NovaDAX — a Brazilian exchange where pairs are priced in BRL, with no auth required for public data.