Legal Due Diligence Document Review with Codex: API Runtime Pattern
A production playbook for legal due diligence document review in legal operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: M&A legal teams and diligence operators
The problem
M&A legal teams and diligence operators need legal due diligence document review to run repeatedly against data room folders, contracts, corporate docs, schedules, and exception lists. In legal operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the legal due diligence document review instructions as a skill, send data room folders, contracts, corporate docs, schedules, and exception lists 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 legal due diligence document review, 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=legal-due-diligence
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo