Rexilion API

Bitcoin metrics API reference for integration teams.

Rexilion API provides API-keyed Bitcoin market and on-chain metric reads, catalog discovery, UTC-bounded historical pulls, and compact t/v responses for research pipelines, dashboards, and model inputs.

Product page Markdown OpenAPI JSON PDF

Quickstart

Base URL

https://api.rexilion.com

Authentication

X-API-Key: YOUR_API_KEY

Metric route

GET /v1/metrics/{category}/{metric}

Example request

GET /v1/metrics/mining/hash_rate_mean?a=BTC&i=10m
Host: api.rexilion.com
X-API-Key: YOUR_API_KEY

Example response shape

[
  { "t": 1718582400000, "v": 62.14 }
]

Coverage

Rexilion API supports 53 public Bitcoin metric routes across 9 groups: market, addresses, blocks, transactions, fees, chain, mining, supply, utxo.

Market

Coinbase spot and Binance spot premium relationships for aligned closed BTC candles.

Addresses

Receiving, sending, and active address counts from standard Bitcoin script/address identities.

Blocks

Block metrics summarize selected Bitcoin blocks inside each closed interval for block production, blockspace use, and block-level fee pressure.

Transactions

Transaction metrics summarize Bitcoin activity in selected blocks: activity, fee-paying activity, size, input, output, and SegWit measures.

Fees

Fee metrics describe transaction-fee activity captured by selected Bitcoin blocks without exposing private source material.

Chain

Chain metrics describe timing behavior across selected Bitcoin block timestamps.

Mining

Mining metrics describe scheduled subsidy, miner revenue, fee mix, and public hash-rate samples for selected Bitcoin blocks.

Supply

Supply metrics describe scheduled Bitcoin issuance and UTXO-set amount snapshots. They do not represent circulating, liquid, exchange, or lost-coin-adjusted supply.

UTXO

UTXO metrics describe selected output-set change, value flow, turnover, and spent-age indicators derived from stored Bitcoin block statistics and UTXO-set snapshots.

Metric catalog

The metric route is GET /v1/metrics/{category}/{metric}. Public Bitcoin series use a=BTC. Market premium routes also use ex=coinbase_spot and ref_ex=binance_spot.

Market

/v1/metrics/market/{metric}

2 metrics. Intervals: 1h. Parameters: a=BTC, i=1h, ex=coinbase_spot, ref_ex=binance_spot.

Addresses

/v1/metrics/addresses/{metric}

3 metrics. Intervals: 1h. Parameters: a=BTC, i=1h.

Blocks

/v1/metrics/blocks/{metric}

8 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Transactions

/v1/metrics/transactions/{metric}

10 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Fees

/v1/metrics/fees/{metric}

6 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Chain

/v1/metrics/chain/{metric}

1 metric. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Mining

/v1/metrics/mining/{metric}

8 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Supply

/v1/metrics/supply/{metric}

4 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

UTXO

/v1/metrics/utxo/{metric}

11 metrics. Intervals: 10m, 1h. Parameters: a=BTC, i=10m, 1h.

Public endpoints

GET /health
GET /openapi.json
GET /v1/assets
GET /v1/metadata/metrics
GET /v1/metrics/{category}/{metric}

Query conventions

Response rules

Real-time data

Rexilion API provides real-time Bitcoin metric data. Clients should treat the latest returned t timestamp as the source of truth for current available data and request trailing UTC windows when polling. This public reference does not publish a fixed latency SLA.

Error map

400 bad_request

Invalid category, metric, interval, asset, or time bounds.

401 unauthorized

Missing, expired, or invalid API key.

403 forbidden

Valid key, but the requested access is not enabled.

429 rate_limited

Request pacing limit reached.

502 source_unavailable

Upstream source is temporarily unavailable.

500 server_error

Unexpected server-side failure.

Access and trust

Rexilion Premium API is listed publicly at USD 299 per month. Premium API accounts have no monthly request cap, with requests paced at 600 API calls per minute for active access.

Teams create a Rexilion account, verify email, activate access, and manage API keys from the authenticated Rexilion profile. API keys are issued after access is active.

Payment collection is provider-hosted through Stripe. Rexilion frontend and backend do not collect raw card data.

Rexilion API does not provide custody, trade execution, investment advice, or guaranteed performance outcomes.