Skip to main content
Answers here are the short version. Each one links to the page that covers the topic properly.

​
Tasks

Yes. A task_id is durable. Read status and output any time, and continue the task with new instructions whenever you want more from it. See The task model.
Continue whenever the request refines previous work: add a column, find more rows, narrow the criteria, fix empty fields. A continued task keeps its plan, rows, and task-local files; a new task starts from nothing. Start fresh only when the goal itself is unrelated. See Follow-up tasks.
A continue submitted while a turn is running is normally queued and returns 202. The legacy 409 task_executing response is used only when queueing is unavailable. Execute is not queued while a turn is in flight. See Errors.
No. The agent always plans. clarify: false means it infers defaults and proceeds without stopping; clarify: true allows one blocking question before execution. See Human in the loop.
No. version applies to the start routes only, and the task stays on that tier for its whole life, including every continue. Read it back as tier on GET /task/{task_id}. See Model tiers.

​
Waiting and reading results

Use the public done field instead of inferring completion from legacy status, phase, or activity. GET /task/{task_id}?wait=50 returns on a status change or after 50 seconds; repeat it until done is true. See Task lifecycle.
Output rows are made of cells. Every field pairs its value with the source it came from: {"value": "Acme", "source_id": "s1"}. Flatten to plain values when you only want the data, and keep the cells when you need provenance. See Outputs and sources.
Keys prefixed with _ are row metadata, not columns: _row_id, _sources, and lineage or validation fields. Skip them when presenting results. Structured output includes a flatten helper that drops them.
No. Streaming is optional. Poll GET /task/{task_id} when you only care about the result, and reach for the SSE routes when you want to watch the agent work. See Live messages.

​
Keys, credits, and limits

Either X-API-Key: YOUR_KEY or Authorization: Bearer YOUR_KEY. Use the full key you copied when creating it; the shortened key shown later in settings is display-only and returns 401. See API overview.
GET /credits returns the balance, and task status responses carry per-task credit usage. A task that runs out of credits fails with 402 and an error of out_of_credits. See Rate limits.
ranger, scout and wren are the only accepted values for version. Anything else returns 422 with {"error": "invalid_request", "param": "version"}. wren is accepted only on admin plans; on any other plan it returns 403 with {"error": "forbidden"}. See Model tiers.
.csv, .txt, .md, and .markdown, up to 10 MB and 10,000 rows. Upload through the presign flow, and send the PUT to the presigned URL without any Autumn auth headers. See Attach a CSV.
Still stuck? The Cookbook walks through complete pipelines, and llms-full.txt packs the whole developer surface into one file you can hand to an agent.