Usage Anomaly Investigation with Claude Code: API Runtime Pattern
A production playbook for usage anomaly investigation in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Growth and infra teams
The problem
Growth and infra teams need usage anomaly investigation to run repeatedly against usage exports, logs, billing events, and customer metadata. 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 usage anomaly investigation instructions as a skill, send usage exports, logs, billing events, and customer metadata 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 usage anomaly investigation, 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=usage-anomaly-investigation
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo