Craton workbench

A thin client over the Craton REST API for the seven verbs. Every panel here is one call from the published route table, made from your browser to the environment you name below; the raw request and the raw answer are on the page beside each result.

Craton outputs technical prices, never quotes; it drafts terms, never offers; it cannot bind, issue, endorse, claim or settle.

Environment

GET /health

Which Craton this page talks to. Everything below is this base plus a path from the route table — there is no second destination.

Not checked yet.

Raw response
—

Your key

POST /signup · GET /account

Every verb below the two public paths needs a key. Paste one you hold, or create a free sandbox account here. The key stays in this tab's memory: this page never writes it to storage and never sends it anywhere except the API base above.

No key set.

A new account's secret is shown once, by the API, in the raw answer below. Copy it now if you want it after this tab closes.

Raw response
—

1. Ingest

POST /ingest → GET /jobs/{job_id} → GET /objects/{object_id}

Any SOV, location schedule or bordereau in, a valid canonical risk object out. The upload is accepted as a job; this panel polls it to completion and then reads the object it produced.

Idle.

Raw response
—

The object

GET /objects/{object_id}

The canonical risk object every other verb works from. Ingest fills this in for you; paste an id to pick up an object you made earlier.

Idle.

Raw response
—

2. Analyse

GET /hazard · GET /events/{peril} → GET /events/{peril}/{event_id}/footprint

What the pinned public record holds (SPEC section 3.2). At a point: exceedance rates from a catalogue extract, or return levels off a gridded daily series. Across a peril: the event catalogue behind a result, and one event's footprint as that record has it — the solutions this build's aggregation rule treats as a single occurrence. Every answer names the snapshot it was computed from, and its limitations come back with it. The catalogue is read unfiltered here; the filters a structure applies take query parameters, and the events page in the docs shows them. Both readings can also be run over an object and recorded on its provenance, with POST /objects/{id}/analyse — the docs page walks it. Accumulation across a set of objects answers on POST /accumulation, which this page has no panel for; its docs page walks it too.

Idle.

Raw response
—

3. Price

POST /objects/{object_id}/price → GET /jobs/{job_id}

A technical price for the object above, with the assumptions that produced it on the face of the answer, and the model and version that produced it named beside the figure.

Idle.

Raw response
—

4. Structure

POST /objects/{object_id}/structures

Cut a candidate structure from the object: layers, triggers, indices and wordings as versioned code. Send nothing and the object's own trigger, financial structure and period are used as they stand; send the blocks below to vary them.

Idle.

Raw response
—

5. Backtest

POST /structures/{structure_id}/backtest → GET /jobs/{job_id}

The structure above against the pinned historical archive. The window is optional and is never silently clipped: one reaching outside the record fails the job with the reason.

Idle.

Raw response
—

6. Monitor

POST /structures/{id}/monitoring · GET /monitoring

Recording a structure is your assertion that it is in force under a transaction executed entirely outside Craton — Craton arranged nothing, witnessed nothing and is party to nothing. Reading it back is a measurement: the structure's own index against the newest pinned snapshot, with the distance to attachment. When a level is reached, what you get is the measurement and nothing that follows from it. Webhooks have no address on this build.

Idle.

Raw response
—

7. Package

POST /objects/{id}/package → GET /packages/{id}

The submission pack (SPEC section 3.7): the exposure summary, the technical price with its complete assumption set, and the backtest exhibit when a backtest of a structure cut from this object is recorded. It is assembled only from runs already in the object's provenance and computes nothing, so price the object first. Every document in it is watermarked as a draft produced by analytics software, and it is execution ready in one sense only — a human takes these documents into their own placement process and executes them elsewhere, never inside Craton. The draft slip the specification also names is not one of its documents yet.

Idle.

Raw response
—

Usage

GET /usage

What this account has run and what has been metered for it. Pricing is usage-based: per object and per model run, on a free sandbox tier, with billing in test mode until the operator flips the switch.

Idle.

Raw response
—