Document Classification with Claude Code: API Runtime Pattern
A production playbook for document classification in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Operations teams routing large file intake
The problem
Operations teams routing large file intake need document classification to run repeatedly against mixed PDFs, emails, attachments, and routing labels. 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 document classification instructions as a skill, send mixed PDFs, emails, attachments, and routing labels 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 document classification, 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=document-classification
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo