The Managed API lives at https://runstamp.com/api/v2. The unified SDK already
handles environment-bound keys, idempotent submission, execution polling, result
reads and cancellation.
Discover and invoke operations
GET /api/v2/operationsdiscovers all public-GA operations.GET /api/v2/operations/:domain/:verbdescribes an exact operation.POST /api/v2/operations/:domain/:verbwithIdempotency-Keysubmits typed input and options as a durable execution.- Poll
GET /api/v2/executions/:id, then readGET /api/v2/executions/:id/result. - Cancel with
POST /api/v2/executions/:id/cancel. Deliver artifacts through the exact-evidence review and release resources.
V1 catalog and synchronous operation routes were removed before launch. Operation names, schemas, deterministic output, typed results, losses and receipts are still defined by the shared registry and worker. The frozen contract describes signed data. Retired routes don't change its bytes.
Preserve original evidence identities
GET /api/v1/artifacts/:id (also /v1/artifacts/:id) reads existing
operation_artifacts. It checks the original organization, expiry, signed
receipt and byte hash. An operation-artifact ID is not a release or execution
ID, and substituting one would invent provenance. Stored rows and signed
receipts stay intact, and no V1 operation HTTP writer remains.
POST /api/v2/preflight still creates render_jobs. Their scoped
GET /api/v2/jobs/:id and /diff projections keep the job and baseline
identities. Diff reads may create visual comparison artifacts. Legacy job
approval and DELETE/cancel writes were removed. They cannot grant review or
release authority.
The removed HTTP license-validation endpoint had no first-party caller. Use
local @runstamp/license validation for signed license keys and offline
certificates. See Licenses.
Public showcases still use their compile and preview routes for bounded anonymous file and preview responses. Governed operations need an active workspace key, idempotency and durable polling. These showcase routes serve a separate journey.