API reference

Metadata

Normalized per-exchange reference data — leverage caps, contract limits, funding, volume, deposit/withdraw and orderbook stats.

Metadata is sourced from cexfeeds and normalized across venues, so the same shape works everywhere. This is the lowest-tier surface — available to every key — because it's reference data, not signal.

`{kind}` is one of `limits`, `funding`, `volume`, `assets`, `orderbook`. `{exchange}` is the lowercase exchange id.

GET {exchange}

Normalized metadata of the given kind for one exchange.

GET/v1/meta/{kind}/{exchange}

Tier: machine-dev+ (all tiers)

Query parameters

ParameterTypeDescription
kindreqpathlimits | funding | volume | assets | orderbook.
exchangereqpathLowercase exchange id, e.g. binance.

Response

json
// GET /v1/meta/limits/binance
{
  "meta": { "trace": "c_4f2a…", "as_of": 1781000000.42, "count": 2 },
  "data": {
    "BTC_USDT": { "max_leverage": 125, "min_qty": 0.001, "tick_size": 0.1 },
    "ETH_USDT": { "max_leverage": 125, "min_qty": 0.01, "tick_size": 0.01 }
  }
}

Event fields

Payloads are curated — only the fields below are exposed. New upstream fields never leak by default (allowlist policy). Every response carries a per-consumer trace watermark.

ParameterTypeDescription
meta.countintNumber of symbols returned in data.
dataobjectSymbol-keyed normalized values for the requested {kind}, e.g. BTC_USDT → { max_leverage, min_qty, tick_size }.