Batch Document Intake with Codex: API Runtime Pattern
A production playbook for batch document intake in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Back-office automation teams
The problem
Back-office automation teams need batch document intake to run repeatedly against folders of documents, classification rules, and target systems. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the batch document intake instructions as a skill, send folders of documents, classification rules, and target systems as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For batch document intake, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=batch-document-intake
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo