Bulk PDF Processing with Claude Code: API Runtime Pattern
A production playbook for bulk PDF processing in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Document automation teams with batch jobs
The problem
Document automation teams with batch jobs need bulk PDF processing to run repeatedly against hundreds of PDFs, schemas, review rules, and output 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 bulk PDF processing instructions as a skill, send hundreds of PDFs, schemas, review rules, and output files as run-scoped inputs, execute with Claude Code, 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 bulk PDF processing, 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=claude-code
workflow=bulk-pdf-processing
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo