Plans & credits
What a credit is, which actions spend one, and where to watch your usage.
Reading and parsing are free; running a simulation costs a credit. This page is the honest accounting of what bills, what doesn't, and how the robustness suite multiplies cost so you can budget before you batch.
What a credit is#
A credit is one backtest. Your plan grants a pool of them per billing period; you can see the
pool at any time under Account → Usage or via GET /v1/usage (limit, used,
remaining, period end).
What costs credits#
| Action | Cost |
|---|---|
| Run a backtest | 1 |
| Parameter sweep | 1 per backtest in the sweep |
| Parameter grid (5×5) | 25 |
| Walk forward, joint sweep, genetic search, strategy variants | a handful each (typically 5) |
| Run a portfolio | 1 per asset in the book |
| Portfolio sweep | values × assets (K × N) |
What's free#
- Parsing a query, reading results and history, sharing a run, exporting to CSV or Pine, and running screener scans don't spend backtest credits.
- Monte Carlo, out of sample split and regime context read the run you already paid for, no extra charge.
- LLM parsing and Pine compilation are gated by plan feature, not metered per call.
Plans#
Tiers, quotas and history/timeframe limits live on the pricing page. Higher tiers raise your monthly allowance and history depth, widen the timeframes and markets you may test, and unlock API access, custom Pine indicators, Pine export and the deeper robustness work.
A free account gets a one time allowance of backtests for the life of the account, not a monthly one. It is enough to judge the product on your own strategy, not to run a research program. Scan alerts and the MCP connector are on every plan, free included; what a higher tier buys there is a larger number of active alerts, and a rolled up digest at the top.
Rate limits#
On top of your credit pool, the API is rate limited to 240 requests/minute per IP and a
per account ceiling set by your plan: 60/minute on Pro, 120 on Power, 240 on Quant and
Enterprise. Over a limit you get a 429. See
authentication for the headers.
The robustness suite runs many real backtests, a grid is 25, a sweep is one per value. Check
GET /v1/usage before a batch, and confirm the cost before a large sweep you didn't explicitly
ask for. Retries are safe: send an Idempotency-Key and a replay returns the original run with
no second charge.
Related: robustness, authentication, pricing.