Skip to main content
All endpoints are under https://api.kiteml.com/v1. Every request needs Authorization: Bearer kite_…, and should send Kite-Version: 2026-10-12 (see versions). This page is the map; each endpoint’s own page, with every parameter, response field, and error, is under the API reference tab. Both are generated from the OpenAPI document at https://api.kiteml.com/v1/openapi.json, so they describe exactly what the API does.

Augmentations

See Augmentations for the full lifecycle, request body, and response shapes.

Account

Filter the request log by outcome with status: 2xx, 3xx, 4xx, 5xx, errors (every 4xx and 5xx), or one status code such as 429. Any other value, failed for example, returns 400 parameter_invalid.

Training runs

See Training runs for the full lifecycle, request body, and response shapes.

Twins

Private beta — see Twins.

RL runs

See RL runs for a worked example, from the request to the policy running in MuJoCo.

Catalog

Operations and webhooks

Events: augmentation.completed, augmentation.failed, augmentation.canceled, training_run.completed, training_run.failed, training_run.canceled, twin.completed, twin.failed, twin.canceled, twin.resumed, rl_run.completed, rl_run.failed, rl_run.canceled, evaluation.succeeded, evaluation.failed, evaluation.canceled, evaluation.resumed, and the account’s usage.threshold_reached and balance.low. twin.resumed and evaluation.resumed are sent after a resume succeeds.

Evaluate (beta)

Beta. These endpoints work today, but they can change before they’re stable, without a new Kite-Version. Changes are announced before they ship. Each one is marked Beta in the API reference tab.
Evaluations were called sim runs (/v1/sim_runs) until October 18, 2026.
The interactive reference at api.kiteml.com/v1/docs is generated from the same OpenAPI spec the API is built on, so it’s always in sync with production.
Every long-running resource answers to GET /v1/operations/:id, whatever its id prefix. If you poll more than one kind of run, write that loop once against operations rather than one loop per resource — the status vocabulary is the same for all of them.