A published Blueprint is a reusable automation whose public surface contains only a display-safe definition and input contract. Integrations can discover active Blueprints and start cloud runs without access to draft authoring data.
Discover a Blueprint
Each resource includes its ID, command, name, description, active status, input declarations, and latest published revision.
Run an immutable revision
Supplying revisionId guarantees that the run uses that immutable published revision. Omit it to atomically pin the latest published revision when the run is created. Every run response includes the chosen revisionId.
Lifecycle
Blueprint runs can report:
queued or running while work is active
waiting_for_approval, paused, or user_controlling when execution is suspended
completed, failed, cancelled, or interrupted when terminal
The SDK wait helpers return on completed, failed, cancelled, or interrupted.
Safe snapshot events
GET /v1/blueprint-runs/{run_id}/events returns at most one display-safe run.snapshot after the requested cursor. It never returns internal node events, browser observations, raw tool data, credentials, or provider details.
Public boundary
The public API does not expose draft creation, graph mutation, validation, testing, or publishing. Those remain authenticated product workflows.
client.blueprints.run() remains a compatibility alias. New integrations should use client.blueprints.runs.create() and the complete runs lifecycle.