Partner Integration Review with Claude Code: API Runtime Pattern
A production playbook for partner integration review in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Partnership engineering teams
The problem
Partnership engineering teams need partner integration review to run repeatedly against API docs, payload samples, auth requirements, and test evidence. 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 partner integration review instructions as a skill, send API docs, payload samples, auth requirements, and test evidence 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 partner integration 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=partner-integration-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo