System and metadata

#Health of the service

The probe. It says whether the service is up and whether its database answers. It is the only route that answers without a key, and it is never counted against the quota, which makes it the point a monitoring system can query without consuming anything.

{
  "status": "ok",
  "server_time": "2026-11-08T12:51:13.156Z",
  "data_type": "health",
  "data": {
    "database": "connected"
  }
}

In case of a problem: 503 with the error body (error.code: "service_unavailable", and database: "unreachable", service and retry_after_s under error.details), and the Retry-After header.

#Freshness of the feeds

One line per data feed, under its public name: its age, the rhythm at which it is expected to publish, and an is_stale flag computed server-side. The rule is the same for every feed: a feed is late when it has not delivered for 1.5 × its expected rhythm. No internal table, no venue name, no row count. It is the route to query before building an analysis: knowing that data is old is better than discovering it in a result. It covers every family: prices and volumes, derivatives, order flow, trades, and also options, on-chain, macro, ETF, tokenomics and sentiment. A slow series is not a late one: a monthly macro series or a quarterly ETF filing legitimately reaches an age of weeks, and its expected_interval_s says so.

{
  "status": "ok",
  "server_time": "2026-11-08T12:51:14.698Z",
  "data_type": "status",
  "data": {
    "computed_at": "2026-11-08T12:51:13.669Z",
    "state": "ok",
    "feed_count": 82,
    "stale_feed_count": 0,
    "error_feed_count": 0,
    "max_age_s": 7649473.7,
    "feeds": [
      {
        "feed": "klines_futures_1m",
        "family": "price_volume",
        "routes": [
          "/v1/klines",
          "/v1/klines/history"
        ],
        "age_s": 73.7,
        "expected_interval_s": 120,
        "threshold_s": 180,
        "is_stale": false,
        "stale_venue_count": 0
      },
      {
        "feed": "klines_1m",
        "family": "price_volume",
        "routes": [
          "/v1/klines",
          "/v1/klines/history"
        ],
        "age_s": 73.7,
        "expected_interval_s": 180,
        "threshold_s": 270,
        "is_stale": false,
        "stale_venue_count": 0
      },
      {
        "feed": "klines_multi",
        "family": "price_volume",
        "routes": [
          "/v1/klines",
          "/v1/klines/history"
        ],
        "age_s": 373.7,
        "expected_interval_s": 660,
        "threshold_s": 990,
        "is_stale": false,
        "stale_venue_count": null
      }
    ]
  }
}

#Symbol catalogue

The live list of the assets enabled. It is the authority: do not hard-code the list in a client, have it read at start-up.

{
  "status": "ok",
  "server_time": "2026-11-08T12:51:15.750Z",
  "data_type": "symbols",
  "data": [
    {
      "symbol": "AAVEUSDT",
      "base_asset": "AAVE",
      "name": "Aave",
      "quote_asset": "USDT",
      "markets": [
        "spot",
        "futures"
      ]
    },
    {
      "symbol": "ADAUSDT",
      "base_asset": "ADA",
      "name": "Cardano",
      "quote_asset": "USDT",
      "markets": [
        "spot",
        "futures"
      ]
    }
  ]
}

#Capability report

What this asset can actually serve, measured over the last twenty-four hours. It makes it possible to anticipate an empty response instead of discovering it, and to tell a metric that makes no sense here from a metric momentarily blocked.

curl -H "X-API-KEY: $BYTNODE_API_KEY"   "https://api.bytnode.com/v1/capabilities?symbol=BTCUSDT"

An unknown or disabled symbol returns 422 invalid_symbol with the list of active symbols.

#Your plan’s limits

What your key may do, read from the plan that served THIS request: the market data families it includes, the history window of each timeframe, the tick-by-tick window, the number of individual liquidations, and the per-minute rate and monthly quota with what is left. Size limit and since_ms from it before paging, instead of discovering the window through a 403 history_depth. Not counted in your quota. With an unmetered key, every limit is null.

curl -H "X-API-KEY: $BYTNODE_API_KEY" "https://api.bytnode.com/v1/limits"