For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pricing

418 billion+ trades across 13 exchanges. REST API and direct SQL access on every tier — including Free. All tiers include spot, futures, and options data; the time window varies.

Tiers

Free (0 EUR)
Developer (39 EUR/mo)
Professional (99 EUR/mo)
Business (299 EUR/mo)
Enterprise (from 1000 EUR/mo)

OHLCV daily/hourly

Full history

Full history

Full history

Full history

Full history

OHLCV 1-min

Rolling 1 month

Rolling 1 year

Full history

Full history

Full history

Spot trades

Rolling 24h

Rolling 90 days

Rolling 1 year

Complete

Complete

Futures data

Rolling 24h

Rolling 90 days

Rolling 1 year

Complete

Complete

Options data

Rolling 24h

Rolling 90 days

Rolling 1 year

Complete

Complete

REST API Limits

Free
Developer
Professional
Business
Enterprise

Items per request

100

1,000

1,000

1,000

Custom

Requests per day

100

100

1,000

10,000

Custom

SQL Limits

Per-month quotas

Free
Developer
Professional
Business
Enterprise

query_selects

50

500

1,000

10,000

100,000

result_rows

50,000

500,000

5,000,000

50,000,000

1,000,000,000

SHOW, DESCRIBE, and EXPLAIN queries are exempt from the queries/month counter.

Shared limits (all tiers)

Type
Limit

execution_time

60 seconds max per query

data_transfer

100 GB per month

After upgrading, reconnect your SQL client so the new quotas and history window apply — see How to connect. REST requests update automatically.

Infrastructure & Enterprise

Free
Developer
Professional
Business
Enterprise

Remote replication

Eligible

Eligible

On-premise

Eligible

Private link

Eligible

Eligible

Pricing methodology (valuation)

Eligible

Support

Free
Developer
Professional
Business
Enterprise

Level

Community

Email

Priority

Priority

Dedicated manager

Time-Window Clamping

A query that partially overlaps your tier's allowed time window returns only the data that falls within the window. For example, a Free-tier user querying 7 days of spot trades receives only the last 24 hours; a Developer querying 2 years of 1-minute OHLCV candles receives only the last year.

On the REST API, a request whose entire range is older than your tier's window returns HTTP 422 with a JSON body — a plain-language message, a ready-to-run example_url inside your window, and a discord_url for help — instead of an empty response. (Live on /ohlcv and /trade.)

If a query returns fewer rows than expected, the requested range likely exceeds your tier's data window. Upgrade your tier to access deeper history.

REST vs SQL

REST and SQL serve different use cases. REST is designed for recent, small data pulls and app integrations. SQL is designed for historical analysis, backtesting, and bulk computation.

For example, downloading 1 year of 1-minute candles for one pair:

  • REST at 1,000 items/req: 526 paginated requests

  • SQL: 1 query, server-side, result in ~1.7 seconds

The REST API is the discovery and integration layer. For any workload exceeding a few thousand rows, use SQL.

Enterprise

For workloads beyond Business tier limits, we offer custom Enterprise plans (starting from 1,000 EUR/mo) with dedicated resources, SLAs, remote replication, on-premise deployment, private link, and pricing methodology (valuation) eligibility. Contact us for details.

Last updated

Was this helpful?