Operations Reference

An operation is the unit of work: a (domain, verb) pair with a declared input schema, output schema, error codes and loss codes. Every operation behaves the same way regardless of which surface you call it from — same input, same result envelope, same codes.

Four surfaces, one catalog:

• SDK — import the package and call the verb off its ./ops export.
• HTTP — POST /v1/{domain}/{verb} on the hosted API.
• MCP — discover with runstamp_list_operations, fetch one schema with runstamp_describe_operation, then execute it through runstamp_invoke_operation.
• Embedded UI — render the result with @runstamp/react.

Two conventions are worth knowing before you read the tables. A deterministic operation returns byte-identical output for byte-identical input, so you can cache it and diff it. A loss code is an operation telling you, up front, what a conversion can take away — an operation that declares no loss codes claims full fidelity and is held to it by conformance gate C11.

{/* START GENERATED OPERATION CATALOG */}

The catalog

79 operations · 12 packages · 5 domains.

A domain is not a package. pdf is served by both @runstamp/pdf and @runstamp/forms, and common by whichever extensions declare it — the operation carries its own private binding, which is why the four surfaces stay uniform without leaking implementation modules.

common — 41 operations

Verbs: convert, extract, inspect, parse, render, transform, validate.

docx — 10 operations

Verbs: convert, diff, inspect, parse, redact, render, transform, validate.

pdf — 17 operations

Verbs: convert, extract, inspect, redact, render, repair, transform, validate.

pptx — 4 operations

Verbs: convert, render, repair, validate.

xlsx — 7 operations

Verbs: convert, inspect, parse, render, repair, transform, validate.

Every operation on every surface

The same operation is reachable four ways. The table is generated from the registry, so a new operation appears on all four the day it is registered.

Failure and loss codes

Every code an operation may emit is declared on its descriptor and enforced by conformance gate C5 — an operation cannot return a code it has not declared. Operations that can lose fidelity declare that too, so a caller can decide before running whether the loss is acceptable.

71 of 79 operations declare at least one loss code.

{/* END GENERATED OPERATION CATALOG */}

What is deliberately not here

merge and split are empty in every domain. They are real gaps, not omissions from this page.

Some capabilities live off ./ops on purpose. @runstamp/review-operations ships three of its eight operations here because the review workflow — add, reply, resolve, project — is a governed service rather than a pure operation. @runstamp/delimited-data ships nine of ten because stream-reconcile synthesises its own rows from a count and never reads a caller's document, which makes it a budget self-test, not an operation.