Banking KYC File Review with Claude Code: API Runtime Pattern
A production playbook for banking KYC file review in banking operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Bank compliance teams reviewing customer onboarding
The problem
Bank compliance teams reviewing customer onboarding need banking KYC file review to run repeatedly against KYC forms, IDs, beneficial ownership records, sanctions notes, and risk policies. 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 banking KYC file review instructions as a skill, send KYC forms, IDs, beneficial ownership records, sanctions notes, and risk policies 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 banking KYC file review, 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-kyc-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo