Build with Craton
From developers, for whoever
your integrator is now.
Plain HTTP, a runnable quickstart, a key in one call — and the walk is performed nightly by an automated agent, so if a machine can onboard from the public docs, so can you.
Get a free API key → Run the quickstart →
try a request
recorded answer
Recorded answers from staging, 2026-08-26 — replayed here so
this page makes no request when you view it. Point the same calls at
$CEDE_BASE_URL and the live environment answers.
Backdrop: Tokyo, Kawasaki and Yokohama at night from the ISS — NASA, public domain.
The surfaces
Four ways in, one API under all of them
Quickstart
Ten minutes, one terminal, no SDK: signup, a key, a schedule ingested, a canonical object read back. Every example is executed against a live environment by CI on every change — the page cannot drift from the product.
The open schema
The canonical risk object as published JSON Schema — read it, validate against it, generate types from it. No account, no key: the same files Craton validates its own responses against.
Playground
The guided browser walk: a spreadsheet in, a risk object, a trigger, a forty-season backtest and a technical price out — with the raw request and raw answer beside every step.
Workbench
A per-verb console for a reader who already holds a key. One panel per verb, nothing hidden, the raw response always in view.
The path
Sign up. Get the key. First object in minutes.
-
Create an account
One unauthenticated call —
POST /signup— or one click. The account and its key arrive in the same response; the secret prints once and is never stored. -
Ingest a schedule
Send the file you actually have. Ingest normalises it into a canonical risk object and writes every guess it made into
source_fidelityinstead of dropping it silently. -
Price it, backtest it
Every verb is a job with an id. A technical price arrives with its model versions, data vintages, event set and loadings as first-class fields, and a backtest replays forty seasons of the pinned record byte for byte.
-
Hold us to it
The onboarding walk is timed by the production checks on every sweep — the measured timings are a page generated from the log, not a promise. The error reference is the complete list of every refusal shape.
Agents are first-class readers
If a machine can onboard, anyone can
Every page of the documentation carries runnable blocks a machine can execute, the schema is served as files a machine can validate against, and the nightly QA cohort — automated personas with real jobs — attacks the product through the same public interfaces you use. The docs are written for that reader first, which is why they stay precise for this one.