Craton has made you a free sandbox account — copy the key if you want it after this tab closes.
Your key
Creating your account…
API key — shown once
Keep it when it prints. Craton stores only its digest, so this is the one and only place the secret ever exists on our side: no later call returns it, nobody can look it up for you, and a lost secret means signing up again.
Why there is no sign-up form
Craton is self-service: no form, no email, no payment details, nobody to ask. The first time you open this page it creates one free sandbox account for you and keeps its key in this browser; it never creates a second one, however often you reload. Start over clears the key from this browser and lets the page create a fresh account next time.
There is one exception, and it is the only one. If the server answers 401 to the key this browser is holding — the account is not one it knows, which is what a key kept from a sandbox that has since been rebuilt looks like — then that record is unusable by any route and nothing exists under it. On the walk's first call the page replaces it once: it forgets the record, creates a fresh sandbox account and sends your file again. Once per visit, never in a loop, and never after the walk has made something the old account owns — in that case the screen says what happened and start over is right there on it.
Account
Raw request and response
—
—
Send a spreadsheet: the sample schedule, or a CSV of your own.
File
No file chosen yet.
—
What leaves your browser
Nothing you choose leaves this browser except as the body of one request to Craton. The sample is the same two-row schedule the quickstart uses: ordinary spreadsheet columns, money written with currency symbols and thousands separators, a peril spelled the way a person spells it.
Ingest job
- queued
- running
- succeeded
Waiting for a file.
Why a job comes back and not an answer
Every Craton verb answers with a job rather than an answer, so a job that takes forty milliseconds and one that takes forty seconds look the same to whatever you write against the API. This panel is that job, moving.
Raw request and response
—
—
Your file is now a canonical risk object — the one document every other verb reads.
Exposure
- Locations
- —
- Values by coverage part
- —
- Peril
- —
What we weren't sure about
- Columns not recognised
unmapped_columns - —
- Units inferred
guessed_units - —
- Rows read more than one way
ambiguous_rows - —
Why the empty lists are printed too
Nothing is dropped silently. A column that did not make it into the object, a unit inferred rather than stated, a row that could be read more than one way — each is named here, and so is its absence, because "we were sure about everything" is itself a claim worth printing.
Locations
Raw request and response
—
—
Pick what pays: Craton attaches the template's index and payout steps to your exposure and cuts a structure.
Trigger templates
Pick a template.
What a trigger is
A trigger-based structure pays on a measurement, not on a loss adjuster's report: something measurable happens inside a stated region, and a fixed fraction of the limit is due. Nothing about your buildings decides the payout — only the measurement the index names.
Structure
Raw request and response
—
—
Craton replays the structure over the pinned archive and shows what it would have paid, year by year.
Replay
Waiting for a trigger.
—
Payout by year, as a share of the limit
—
Raw request and response
—
—
The technical price, and every assumption that produced it.
Technical price
Waiting for a backtest.
—
How it was built up
The same walk from a terminal
Everything here is doable from a terminal in the same number of
calls, against the same routes: the quickstart page in Craton's docs
walks it in curl. What you have at the end of either is
an analytic result and the assumptions under it — take those to your
own broker, captive or panel.
Raw request and response
—
—