Signed URL Delivery with Claude Code: API Runtime Pattern
A production playbook for signed URL delivery in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Teams shipping downloadable agent outputs
The problem
Teams shipping downloadable agent outputs need signed URL delivery to run repeatedly against artifact manifests, expiry policy, and customer permissions. 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 signed URL delivery instructions as a skill, send artifact manifests, expiry policy, and customer permissions 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 signed URL delivery, 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=signed-url-delivery
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo