Maximum size, in bytes, of a single dataset version as stored, that is the bytes of its ready version. For a CSV upload that is the converted file, not the file you upload, so estimate from the number of rows. The Datasets guide has the details.
Maximum number of active datasets your tier allows.
Maximum number of strategy executions (and sweeps) you can have running at the same time
through the API. Starting one past this number is answered with 429, whose message
carries the same number. The value already includes any API allowance your plan has.
Maximum length, in hours, of the time range of one dataset import from an exchange.
Maximum length, in days, of the time range of a backtest on one of your own datasets.
Largest full grid, in parameter combinations, a sweep may run with the grid sampler.
A grid with more combinations is refused with 400; the random and lhs samplers run
only their samples and are not held to it.
Maximum combined storage, in bytes, across every dataset, strategy-execution signal,
and registered strategy on your account — one shared pool, not a separate cap per
resource type, since they all compete for the same underlying storage. See GET /account/usage's storageBytesUsed for your current usage against this number.
Your current subscription tier.
Your account id — the JWT sub claim.
Your identity and tier limits. No database call behind this one — safe to fetch on every page load. Live usage against these limits is a separate resource,
GET /account/usage, deliberately: usage changes on every upload/execution and costs a query to compute, this one doesn't.