Pricing
Two units. Nothing else.
Start free, no payment details. Beyond the
sandbox allowance: per object, per model run — the same two units
GET /usage reports.
Get a free API key → How the meter works →
No payment details at signup The free allowance never date-expires Test mode until launch — no live charge is possible
The rate card
| per object — Ingest or Structure stores one | $0.25 / object |
| per model run — Price, Backtest, or a registry model run | $1.00 / run |
| every read route, Package, Analyse rollups | free |
| sandbox plan at signup | free |
| private registry | from $499 / month |
The caller pays for model runs; authors are never charged for use of their models. A metered event is recorded on success only, inside the job that did the work, and the invoice must equal the meter exactly — that equality is recomputed by CI from a recorded run on every change. Usage, and cancelling is the runnable page that reads the meter back.
Estimate a month
A planning aid, not an invoice: it multiplies the two published
unit rates and knows nothing about your account, its remaining free allowance, or
what you will actually run. The meter, read back at GET /usage, is the
record.
What the free sandbox is
Every account starts on the sandbox plan: a
lifetime allowance of free units — 500 on the product’s default
configuration — that counts down as you use it and never expires on a date.
Allowance-covered usage is still metered and still itemised, at a unit amount of
zero, so the first invoice you would ever pay is shaped exactly like the free ones
you already saw. Cancelling is self-service and immediate:
DELETE /subscription stops the meter and the billable verbs, and
GET /usage keeps answering.
On the staging environment behind these pages the allowance is deliberately set to zero, so the paid half of the billing lifecycle is exercised where exercising it is free of consequence — billing runs at the payment processor in test mode, and no live charge is possible until the operator turns real billing on.