task_id, its own sandbox and agent, task-local files, streamed
events, and output rows you can fetch any time. Start a task, walk away, and come back to
results. When you need changes, continue the same task instead of starting over.
Autumn is one HTTP API. Start with the Quickstart, read the
Task API for every route, or install the Skill to give another
agent the same task surface.
Quick start
task_id. Keep it. Use it to stream events, continue the task,
read status, and fetch output.
The model
Autumn exposes one public primitive: a task. You hand it a goal; it plans, works the web, and writes output rows you can fetch any time. One planning flag,clarify, decides
whether it may stop to ask a question first.
The task model covers this properly: start modes, turns, and why
continuing a task beats starting a new one.
When to use Autumn
Reach for Autumn when the work is too big or too slow for a single chat turn and you want it done end to end:- finding or enriching companies, people, jobs, filings, pages, or contacts
- collecting rows with sources and evidence
- scraping or checking multiple public sources
- continuing a previous task without starting over
- producing output files or task-local artifacts
API key
Create an API key in Autumn settings under API, then keep it in an environment variable:X-API-Key or Authorization: Bearer. See
Authentication.
Next
Quickstart
Start a task, wait for it, and read the rows.
Task API
HTTP routes for starting, streaming, continuing, and reading tasks.
Skill
Install the Autumn skill in Claude Code or any agent that reads skills.
Vibecoding
Drop Autumn into your coding agent with one link.