Opus 5.5 batch savings come with a deadline for collecting results
Anthropic's discounted batch service requires teams to reconcile individual outcomes and retrieve results within 29 days of creation, even when processing finishes later.
Claude Opus 5.5's batch prices favour work that can wait: Anthropic lists $2 per million input tokens and $10 per million output tokens, half the standard rates. Operations teams also inherit a result-retrieval deadline.
The batch guide says most jobs finish within an hour, but unfinished requests expire after 24 hours. Results remain downloadable for 29 days from creation, not from completion. A batch marked ended may contain successful, failed, cancelled and expired requests.
That distinction matters when importing results into a business workflow. Output order is not guaranteed; each result must be matched through its custom_id. Treating the whole file as a successful run can hide missing records.
Anthropic also says batch processing stores request and response data for up to 29 days. Completed batches can be deleted; an active batch must first be cancelled. The discount therefore comes with timing, reconciliation and storage decisions rather than a guarantee of immediate output.
프리즘코리아 편집국 > Daniel Reed
