CRATON Get a free API key

The product · the engine

Seven verbs. One engine.

Every verb is a job with an id; every result is labelled with the model and data that produced it. All seven answer on this build — GET /health is the roster.

Get a free API key Run the first verb

Backdrop: Typhoon Phanfone, western Pacific, 3 October 2014 — Terra/MODIS, NASA, public domain.

The pipeline

A file in, receipts out

The pipeline: a file becomes a canonical risk object through ingest; analyse, price, structure and backtest, monitor and package run over it; every result carries its receipts.
ingestAny SOV, location schedule or bordereau in; a valid object out — every guess named in source_fidelity.
analysePoint hazard lookups, the event catalogue and footprints, accumulation across a set of objects.
priceA technical price with model versions, data vintages, event set, loadings and currency basis attached.
structureCut a candidate structure from an object — its terms, addressable on their own.
backtestReplay a structure over forty seasons of the pinned record, year by year, byte for byte.
monitorRecord a structure as in force and read the measurement: index value and distance to attachment, plus webhooks with delivery logs.
packageAssemble the submission pack from runs already on the object’s provenance — every document watermarked draft.

A backtest you can point at on a map

Forty seasons. Six occurrences paid.

The home page’s boxed-region structure, drawn where it lives: the bounding polygon off the Kanto coast, and the six catalogue events whose magnitude reached the trigger across 1986–2025 — each dot a real occurrence from the pinned quake catalogue, sized by magnitude.

The Kanto earthquake-box polygon with the six catalogue events that paid in the forty-season backtest, 1987 to 2023.

Epicentres and magnitudes from the pinned catalogue (usgs-eq-kanto, vintage 2026-08-10) via GET /events/earthquake; the box from the home page’s object; the coastline stylised. Backtest a structure reproduces the whole run.

Every verb, a runnable page

The docs execute themselves

Each verb has a guide whose examples CI runs against a live environment on every change — a page that stops working stops the merge. Start anywhere: a technical price from nothing, a backtest, an analysis, a recorded structure measured, or the draft pack assembled.

All the guides