Commercial terms
Three tiers, and what each is enforced to carry. The products stay free; the API and the data are what is licensed; a figure comes from a conversation rather than a rate card.
Free, Teams, Enterprise
Free is the Terminal and Atropos in a browser: no account, no key, no API access, and they stay that way. They are the evidence for everything else — a paywalled accuracy record would be worth nothing.
Teams is programmatic access: one organisation, keys issued in the workspace, every documented endpoint, at the platform's standard limits. Limits are per key, so a team that needs more capacity takes more keys.
Enterprise is everything agreed per contract: a higher rate per key, bulk extracts and redistribution rights, EU data residency, an availability commitment with credits, named contacts, and the Enterprise Service Addendum that binds it. Custom on every line, and written down.
There are no prices on this page. What an extract may be used for depends on the licence of the sources behind it, and that varies by corridor; what an integration costs depends on its scope. You will get a fixed number in writing before anything is signed, and nothing is invoiced before that. Tell us what you need and you will have a real answer within two business days.
| Free | Teams | Enterprise | |
|---|---|---|---|
| Who it is for | Anyone, in a browser | One team integrating the feed into a dashboard, a model or an alert pipeline | An organisation that needs contractual commitments, redistribution or residency |
| The Terminal and Atropos | Yes | Yes | Yes |
| API access | No — the fifteen open paths only | Every documented endpoint | Every documented endpoint |
| Rate limit, per key | — | 600 a minute | 6,000 a minute, enforced by a dedicated limiter; more as additional keys |
| Rows per response | — | 5,000 | 5,000 per page; bulk data as extracts up to 25,000 rows each |
| Bulk extracts (CSV / JSON) | No | No | Yes, through the read:exports scope, for redistributable sources |
| Redistribution rights | No | No | Per source, written into the agreement |
| Keys | — | Issued and revoked in the workspace, with scopes, expiry and an IP allow-list | The same, plus the full request log on request |
| Per-key usage summary | — | Yes | Yes |
| EU data residency | — | No | Yes: a project in an EU region provisioned within one business day of the order — how |
| Availability commitment | None | None | 99.9% monthly, with credits — the schedule |
| Support (Sev-1) | Best effort | 4 business hours | 1 hour, 24/7, two named responders |
| Named contact | No | No | Yes — the engineer who built it, and a commercial contact |
| Security questionnaire | — | Completed in writing within 5 business days | Completed in writing within 5 business days |
| DPA | — | Standard, incorporated by reference | Ours countersigned, or yours |
| Source-code escrow | — | No | On request, through an escrow agent |
| Cost | Free, permanently | Quoted | Quoted |
Every tier is the same data. The difference is what you may do with what you take, and what we commit to in writing. The support targets are the ones on support, the availability commitment is measured as availability describes, and every number in the table comes from the same endpoint the software enforces it from. This table says what those pages say, on purpose.
A real key, before anything is signed
Ask through the form, choosing “API access”. A Teams key is issued by hand within two business days, time-boxed, every documented endpoint, no card and no invoice. When the trial ends the key expires; nothing renews on its own.
Priced per engagement, and why
Four things are quoted individually rather than listed, and the reason is the same each time: what they cost us varies with what you actually need.
| Bulk extracts | An extract is redistribution — a file you keep. Two of our 55 sources forbid it outright and seven restrict commercial reuse, so the terms depend on which corridors you need and which licences sit behind them. See the source classification. |
| Corridor validation | We backtest your corridor — your ports, your suppliers, your lanes — against the same harness that produces the public accuracy record, and you see the result before you commit. Scoped by the number of corridors and the history required. |
| A private feed | Sources we do not currently carry, ingested and attributed to the same standard. Scoped by the ingestion work. |
| Integration | Into your own graph, warehouse or alerting. Scoped by the work. |
How the commercial relationship works
| Billing | By invoice, in advance, monthly or annually as agreed. There is no card payment path. |
| Minimum commitment | None on Teams. Agreed on Enterprise. |
| Termination for convenience | 30 days on Teams. As agreed on Enterprise. |
| Price changes | Never inside a committed term. 60 days' notice before a renewal. |
| Breaking API changes | 90 days' notice by email to every active key holder, and in the changelog. A Deprecation response header on the affected endpoint is planned and not yet implemented. |
| What governs | The Terms and, for a licensed key, an order form that takes precedence over them; on enterprise agreements, the Enterprise Service Addendum. The DPA applies to all of it. |
Four steps
- Ask for a trial key through the form, choosing “API access”.
- Send your security questionnaire. Completed in writing within five business days — CAIQ, SIG Lite or your own spreadsheet. The trust centre answers most of it before you ask.
- Have us validate your corridor. Your lanes, scored the same way as the public record, before you commit to anything.
- Sign. A fixed figure in writing first; our DPA is ready to execute, or we will countersign yours; an enterprise order form incorporates the addendum.