{ lossPolicy, signal, context }Developers
One operation contract. Every surface.
Discover registered document operations, invoke them through SDK, hosted HTTP, or MCP where available, and resolve the same typed result envelope.
managed jobPOST /v1/docx/diff
Authorization: Bearer $RUNSTAMP_API_KEY
Idempotency-Key: $YOUR_IDEMPOTENCY_KEY
{ "input": [base, candidate] }
→ { ok, value, losses, diagnostics, receipt }Invocation contract
The operation name and result semantics survive every invocation surface.
{ ok, value, losses, diagnostics, receipt }Runtime sequence
Discover, invoke, resolve.
The calling surface changes; the operation name and result semantics do not.
- 01
Discover
Read the registry descriptor, schemas, stability, and declared behavior.
GET /v1 - 02
Invoke
Pass native bytes and typed options through the surface available to the operation.
operation - 03
Resolve
Handle value or error, losses, diagnostics, and receipt from one envelope.
result
Availability
Claims follow the registry.
Hosted and agent exposure follows each operation descriptor; local package support does not imply every other surface.
Inspect current capability evidence