Maximum size, in bytes, of a single dataset version.
Maximum number of active datasets your tier allows.
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.