Data Room Indexing with Codex: API Runtime Pattern
A production playbook for data room indexing in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Deal teams and diligence operators
The problem
Deal teams and diligence operators need data room indexing to run repeatedly against folders of PDFs, spreadsheets, and evidence files. 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 data room indexing instructions as a skill, send folders of PDFs, spreadsheets, and evidence files 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 data room indexing, 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=data-room-indexing
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo