Signed URL Delivery with Claude Code: Result JSON Schema

A production playbook for signed URL delivery in cross-industry operations using Claude Code: result json schema, 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

Define the outer result contract once, let the signed URL delivery skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. 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.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "signed URL delivery completed",
  "body": { "type": "signed_url_delivery", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo