What TILLA is, who it's for, and how to start. No API key needed.

The newest 1-minute bar and the tiers served. No API key needed.

The public plans: price, history cap, request limits and size. No API key needed.

Exactly what the caller's key holds. No arguments: every lane per layer with its series count. layer=raw|derived|node and lane=1min|hour|daily|...: every series name there. Call this before tilla_latest / tilla_window and use the names it returns. Needs TILLA_API_KEY.

A window of bars. Name exactly what you want, one of: series = comma-separated names (at most 200) from tilla_inventory, or a pattern like 'btc_*' / '*_close'; or markets + fields ('btc,eth' + 'close,volume' -> btc_close, btc_volume, eth_close, eth_volume). layer = raw | derived | node | deep; lane = 1min, 5min, hour, daily, ... start/end = 'YYYY-MM-DD[ HH:MM[:SS]]' UTC inclusive, or period = 30d 2m 6m 1y all; no start = the newest bars. limit <= 50000. When more is true, call again with start = next_start. Needs TILLA_API_KEY.

The newest bar of the named series on one lane. Needs TILLA_API_KEY.

The caller's plan and budget right now: tier, history days, limits, used today. Needs TILLA_API_KEY.

Every market TILLA carries - crypto, US stocks and ETFs, FX, macro - with its category, its related markets, how many series each plan holds of it, and its lanes. No API key needed. Use the id with tilla_market.

One market in one call: every series of market (an id from tilla_markets, e.g. btc, nvda, eurusd, gold) the key holds on lane, on one clock. layer = raw | derived | node | deep | all. related=True adds its connected markets (btc: its ETFs and miners). period = 1d 7d 30d 2m 3m 6m 1y 2y 3y all. At most 200 columns an answer: series_next_offset names the next page. Needs TILLA_API_KEY.

The free sample of one plan (free, builder, pro or max), no key needed: how many series it holds on every lane, and one aligned 1-minute row of real values. The full one-tick files are at /v1/sample/.csv and .db (named in the answer's files).

The newest bar of every lane on every layer - is the data current? No API key needed.

The whole API manual in one call, no key needed: every call, every parameter, every plan, how paging, tick, resume, changes and bulk work. Read this first when you need to know how to do anything.

Your whole plan, live, in one call: every series the key holds on every lane that closed at a boundary (at = 'YYYY-MM-DD HH:MM', default the minute just closed). Per lane: bar, complete, series, values. Needs a key.

Every value our checks repaired since since ('YYYY-MM-DD HH:MM:SS') that the key holds, with its value now - apply them and a kept copy stays correct. Pass the answer's until as the next since. Needs a key.