Platform API reference: endpoints, methods, and paths

All endpoints are under https://api.kiteml.com/v1 and require a Bearer token. Full request and response schemas are published as OpenAPI at https://api.kiteml.com/v1/openapi.json, rendered at /v1/docs.

Augmentations

Method	Path	Description
`POST`	`/v1/augmentations`	Start a run (`source`, `instructions`, `config`, `output`)
`POST`	`/v1/augmentations/estimate`	Estimate the token cost of a run before starting it
`GET`	`/v1/augmentations/:id`	Status, progress, and — when done — output files
`GET`	`/v1/augmentations`	List your runs
`POST`	`/v1/augmentations/:id/cancel`	Cancel a running augmentation

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

Account

Method	Path	Description
`GET`	`/v1/keys/me`	Identity and scopes for the current API key
`GET`	`/v1/usage`	Token usage over a date range, grouped by resource
`GET`	`/v1/credits`	Current credit balance

Training runs

Method	Path	Description
`POST`	`/v1/training_runs`	Start a run per policy (`dataset`, `policies`, `hardware_tier`, `config`)
`POST`	`/v1/training_runs/estimate`	Estimate the token cost of a run before starting it
`GET`	`/v1/training_runs/:id`	Status, phase, live metrics, and output
`GET`	`/v1/training_runs`	List your runs
`GET`	`/v1/training_runs/:id/logs`	Tail the trainer’s output
`GET`	`/v1/training_runs/:id/checkpoints`	List the checkpoints a run saved
`GET`	`/v1/training_runs/:id/checkpoints/:step/download`	Download one checkpoint as a ZIP of its `pretrained_model/`
`POST`	`/v1/training_runs/:id/cancel`	Cancel a run and release its GPU

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

Catalog

Method	Path	Description
`GET`	`/v1/training_policies`	Policy types you can train, and the GPU each one needs
`GET`	`/v1/hardware_tiers`	GPU tiers, with the token rate each one bills at
`POST`	`/v1/datasets/inspect`	Check a dataset is trainable and read its camera keys

Operations and webhooks

Method	Path	Description
`GET`	`/v1/operations/:id`	Uniform status for any run, by id prefix (`aug_`, `trn_`)
`POST`	`/v1/webhook_endpoints`	Register a receiver for run events
`GET`	`/v1/webhook_endpoints`	List your receivers
`DELETE`	`/v1/webhook_endpoints/:id`	Remove a receiver
`GET`	`/v1/events`	The durable event log, so polling is always a fallback

Events: augmentation.completed, augmentation.failed, augmentation.canceled, training_run.completed, training_run.failed, training_run.canceled.

Evaluate

Coming soon. Simulation evaluation endpoints aren’t on /v1 yet. Evaluation runs are available today from the dashboard and the Kite CLI.

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.

​Augmentations

​Account

​Training runs

​Catalog

​Operations and webhooks

​Evaluate

Augmentations

Account

Training runs

Catalog

Operations and webhooks

Evaluate