Batch Api

Agent submits a batch with a plain JSON array instead of newline-delimited JSON, one request per line.

Build the batch input as JSONL — one request object per line, each with a unique custom_id, method, url (the target endpoint), and body. Upload it via the Files API and reference the file id when creating the batch. A JSON array is not valid JSONL.

Agent relies on output line order to map batch results back to source rows instead of custom_id.

Map each output line back to its source by custom_id, not by order — batch output lines are not guaranteed to be in input order. Pick a stable, unique custom_id (e.g. a row UUID) so partial or reordered results still reconcile.

Agent polls batch status every second and treats 'in_progress' as completion when the request_counts show some succeeded.

Poll the batch status with backoff and only treat documented terminal states (completed/failed/expired/cancelled) as final. Partial request_counts during in_progress are not completion. Read the output and error file ids only once the batch reaches a terminal state.