List a project's runs
Returns the project's runs, newest first, with their token and sandbox-time counters. Use it to render run history; use the events endpoint for what happened inside one run.
Returns the project's runs, newest first, with their token and sandbox-time counters. Use it to render run history; use the events endpoint for what happened inside one run.
Path Parameters
The project whose runs to list.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/projects/string/runs"{ "runs": [ { "id": "string", "projectId": "string", "status": "queued", "prompt": "string", "model": "string", "recipeId": "string", "steps": 0, "tokensIn": 0, "tokensOut": 0, "sandboxMs": 0, "error": "string", "startedAt": "string", "finishedAt": "string", "createdAt": "string" } ]}Delete a project DELETE
Soft-deletes a project: it stops appearing in every read immediately, while the row stays until the cleanup job has destroyed its sandbox and stored objects. A delete is therefore idempotent from the caller's point of view — deleting an already-deleted project answers 404.
Start a run POST
Accepts an instruction and queues a run against the project. The response is returned as soon as the run is recorded, not when it completes: the client then follows progress on `GET /projects/{projectId}/runs/{runId}/events` (paged) or the SSE stream. A project has at most one queued-or-running run at a time; starting a second answers 409 until the first finishes or is cancelled. Name a `recipe` to run one explicitly; a recipe this deployment has disabled is refused with 403 `recipe_disabled` and nothing is queued.