Skip to main content
By default Autumn infers the shape of its output from your prompt. When your app already knows the columns it wants, declare them with output.schema on POST /task/start and every row comes back in that shape.

Field types

schema is a flat map of column name to type. Supported types: schema_order fixes column order for readback and exports. Keep the schema flat: one row per entity, one column per fact.

Reading typed rows back

GET /task/{task_id}/output returns rows whose fields are cells, not bare values. Each cell pairs the value with the source it came from:
Flatten the cells when you want plain data, and keep _sources when you need to show or audit provenance:
Validate the flattened rows against your own types (Pydantic, Zod, or whatever your app already uses) and drop rows that don’t fit.
Keep output singular. If the artifact you want changes later, continue the task and replan rather than sending a second output. Outputs and sources covers why.

Output kinds

kind tells Autumn what sort of artifact it is building: research, person, or company. See Outputs and sources for what each one is for.

Task API

The full task spec, field by field.

Follow-up tasks

Add a column to results you already have.