{ lossPolicy, signal, context }Hosted API
One stable HTTP contract for documents.
Authenticate once, discover public operations, invoke managed jobs, and keep artifact and evidence state explicit through the complete lifecycle.
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
Managed execution should add durability—not invent a second product model.
{ ok, value, losses, diagnostics, receipt }Runtime sequence
Discover, invoke, resolve.
The calling surface changes; the operation name and result semantics do not.
- 01
Discover
GET the public registry instead of hard-coding undocumented behavior.
GET /v1 - 02
Invoke
Submit the typed payload with idempotency, cancellation, and tenant context.
POST /v1/:op - 03
Resolve
Receive the result envelope, artifact reference, losses, diagnostics, and receipt.
result
Availability
Claims follow the registry.
Hosted availability follows the capability registry and must not be inferred from local package support.
Inspect current capability evidence