Who it’s for · platform engineers
Adopt the format,
not a vendor.
The schema is open and needs no account: normalise to the format, keep your stack, take the hosted verbs when you want them.
Use the schema, no account → Or get a free API key →
Backdrop: the night lights of Tokyo, Nagoya and Osaka from the ISS — NASA, public domain.
The integration
A schema first, an API second
-
Read the schema like any other file
/schema.jsonis the canonical risk object as published JSON Schema — versioned so a minor bump never invalidates an object you already hold, and served byte for byte as the release carries it. -
Validate in your own CI
The published
validate.pychecks a document against the schema with nothing but Python 3 and the directory — the same files Craton validates its own responses against, so conformance means the same thing on both sides. -
Normalise once, integrate anywhere
Every team that speaks the canonical object can hand risks to any other. The format costs nothing to adopt and never expires; the engine, the normalisation and the hosted verbs are the paid half.
-
Plain HTTP when you want the engine
No SDK: every verb is a route with a documented, CI-executed example, every long verb is a job with an id, and every refusal shape is in the error reference.
In the browser instead
See the whole walk before you write a line
The playground performs the full path — file to object to trigger to backtest to technical price — against staging, with the raw request and raw answer beside every step. The workbench is the same API as a per-verb console once you hold a key.