KetQatKetQat
10-minute guide

Quickstart

Install, run a real benchmark, publish it, and see it compared -- all from the command line.

1Install the SDK

The local runner needs Python 3.10+. Install with the QEC extra to get real Stim and PyMatching execution (no synthetic fallback is used):

pip install "ketqat[qec]"

2Run a benchmark locally

The SDK ships example manifests. This runs a real surface-code memory experiment with MWPM decoding via PyMatching:

git clone https://github.com/ketqat/ketqat-sdk
cd ketqat-sdk
ketqat run examples/qec/surface-code-memory.yaml --output run.json

run.json now contains real metric points and a canonical reproducibility hash computed from the manifest, environment, and results.

3Create an API token

Sign in with GitHub, then create a token in Settings. Tokens are shown once and stored hashed.

4Publish the result

curl -X POST https://ketqat.com/api/runs/import \
  -H "Authorization: Bearer kq_..." \
  -H "content-type: application/json" \
  -d @run.json

The server independently recalculates the reproducibility hash and rejects the import if it doesn't match your submitted result -- so a published run can't silently drift from what you actually ran. Byte-for-byte repeated imports return the existing run instead of creating duplicates. Add {"result": ..., "visibility": "PRIVATE"} as the body instead to publish privately first.

5See it on the leaderboard

Your run now appears on your dashboard, at its own /runs/<slug> page with a downloadable reproducibility bundle, and -- if it's against a standard QEC suite -- on the decoder leaderboard, compared only against other runs on the exact same benchmark suite and version.

Reproducing someone else's run

Every run page has a "Reproduce this" command and a downloadable bundle with the exact manifest, environment, and reproducibility hash used. Reproducing a result is the same one-line ketqat run command -- no special tooling needed.

Full API reference and manifest schema: github.com/ketqat/ketqat-sdk.