Tasks and batches

A task holds the code, its defaults and its schedule — and every run of it adds up under one id.

Task ids

Any run can carry a task_id. Nothing needs to exist first — runs sharing an id already add up on /costs. Saving one as a task keeps the code and lets it run on a schedule.

Schedules

A schedule is a task with an interval, set on the task's own page. The page shows the monthly ceiling implied by the interval and the per-run cap, because that multiplication is where surprises come from.

Batches

opsen batch invoice-extract inputs.txt --cap 5.00 --width 5

One run per line, --width at a time. Each run gets its line as OPSEN_INPUT, so the agent does not need to know it is part of a batch. --cap bounds the whole batch; the task's own cap still applies to each run.

Which model for this job

A task page compares models on that task's own runs — success rate, cost per run, and a lower bound that accounts for sample size. Two runs out of two is 100% and almost no information, so opsen does not recommend from it until there are enough runs on more than one model.