One call for document work:
const result = await runstamp.run(operation, input);The operation names the job. The input holds the document, data or instructions. The result holds the finished value or file, or an error your app can act on.
The basic flow
- Choose the job. Find the operation your customer needs.
- Send the input. Pass the document, data and options that operation requires.
- Handle the result. Return it, continue the workflow, or send a problem to review.
Document jobs
Operations cover:
- creating documents from data or templates;
- reading text, structure, tables, fields, and metadata;
- changing, converting, merging, splitting, repairing, or redacting files;
- validating documents and comparing versions;
- packaging results for downstream use.
See the operation catalog for the current list. For managed workflows, the separately GA Platform control plane adds review, approval, release, delivery, webhook, billing, usage, notification and audit around those results.
Choose where it runs
| Option | Use it when |
|---|---|
| Local SDK | You want the stable catalog in your app or CI. |
| Local MCP tools | An agent should find and run the stable local operations. |
| Managed API | You want Runstamp to run the infrastructure. Needs a free-trial workspace or an active Platform or Enterprise workspace. |
Availability is listed per operation and surface. All stable operations are generally available through local packages, SDK, CLI, MCP and the Managed API. Platform workflows are generally available through the authenticated control plane.
Current local families
The stable public local runtime covers DOCX, XLSX, PPTX, PDF, PDF forms, review operations, and provenance.
For agent access, see MCP Server. For managed processing, see the hosted API guide.