CRATON
Get a free API key

Free sandbox

Your own API key

No form and no email: this browser now holds a free sandbox key.

Making your key…

Your 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.

The walk

  1. Send a spreadsheet

    One of our samples, or your own CSV.

  2. Read it back

    One risk object, with anything unclear named.

  3. Choose a trigger

    What has to happen for it to pay.

  4. Backtest it

    What it would have paid, year by year.

See the API call
Request
Nothing sent yet.
Response
Nothing back yet.

Your spreadsheet

Send a spreadsheet

Use one of our sample schedules, or a CSV of your own.

No file chosen yet.

What leaves your browser

Only the file you choose, as the body of one request to Craton. The sample is the 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. The earthquake sample is the same shape, with two Bay Area sites and Earthquake in the peril column, so the next steps show earthquake boxes instead of hurricane gates. The hail sample does the same for hail, thunderstorm wind and tornado boxes, measured on NOAA's storm reports. The wildfire sample leads to boxes measured on the fires the USGS and the US Forest Service have mapped, and the grid outage sample to county indexes that count how many customers were without power. The typhoon sample leads to gates over the US Joint Typhoon Warning Center's tracks across Asia, the Indian Ocean and the southern hemisphere; the rainfall sample to rain gauge indexes; and the flood sample to the Bow River gauge in Calgary.

schedule.csv

Ingest job

  1. Sending
  2. Queued
  3. Running
  4. Done

Waiting for a file.

See the API call
Request
Nothing sent yet.
Response: the job
Nothing back yet.

From your file

 

locations, read into one risk object: the document every other Craton verb reads.

 

What we weren't sure about

  • Columns not recognizedunmapped_columns 
  • Units guessedguessed_units 
  • Rows read two waysambiguous_rows 
Why the empty lists are shown 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.

    See the API call
      Request
      Nothing sent yet.
      Response: the risk object
      Nothing back yet.

      Map: Natural Earth 110m land, public domain. At this zoom the coastline is approximate.

      Your risk object

      Choose what pays

      A trigger pays when a measured value, like wind speed or quake size, crosses a set level.

      Pick a trigger to use it.

      How it pays
        Pays by strength
          See the API call
          Request
          Nothing sent yet.
          Response: the structure
          Nothing back yet.

          Your trigger

          What it would have paid, replayed year by year over the pinned record.

          Waiting for a trigger.

          Backtest job

          1. Sending
          2. Queued
          3. Running
          4. Done
              The same walk from a terminal

              Every call on this page works from a terminal against the same routes, and the quickstart walks them in curl. Either way, you end with the backtest and the record it was replayed over.

              See the API call
              Request
              Nothing sent yet.
              Response: the backtest
              Nothing back yet.

              Your sandbox

              Account

                Environment

                • production
                • API

                This browser forgets the key, and the page makes a fresh free sandbox account.

                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.

                There is one exception. 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. 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 puts Start over right there on it.