Banking: Suspicious Activity Review Packet with Claude Code: API Runtime Pattern
A production playbook for suspicious activity review packet in banking operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Financial crime teams
The problem
Financial crime teams need suspicious activity review packet to run repeatedly against transaction exports, customer profiles, alerts, case notes, and SAR criteria. In banking operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the suspicious activity review packet instructions as a skill, send transaction exports, customer profiles, alerts, case notes, and SAR criteria 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 suspicious activity review packet, 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=banking-suspicious-activity-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo