Insurance: Subrogation Packet Assembly with Claude Code: API Runtime Pattern
A production playbook for subrogation packet assembly in insurance operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Insurance recovery teams
The problem
Insurance recovery teams need subrogation packet assembly to run repeatedly against claim records, repair invoices, police reports, photos, and correspondence. In insurance operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the subrogation packet assembly instructions as a skill, send claim records, repair invoices, police reports, photos, and correspondence 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 subrogation packet assembly, 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=insurance-subrogation-packet
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo