One workflow. Three ways in.
Use the browser, integrate the REST API, or connect an MCP client. They share the same document processing capability.
REST
Build into your application.
Upload a file, create a job, poll its status, and download the result.
MCPConnect your agent.
Two explicit tools: redact_file and get_result. Existing files are uploaded through REST.
LLM-READABLEGive your assistant the contract.
Markdown documentation, tool definitions and a downloadable OpenAPI description.
PYTHONStart with real HTTP calls.
No invented SDK. A requests example covering the complete asynchronous flow.
01Upload
POST /v1/files02Redact
POST /v1/redactions03Retrieve
GET /v1/redactions/:id/fileStart in your own environment
Python
requests · REST · bounded polling
Node.js 22+
fetch · REST · no dependencies
cURL + jq
shell · full upload-to-download flow
Python + MCP
initialize · tools/list · tools/call
The lifecycle
Upload → queued → running → completed → authenticated download
A failed job returns an error. Receiving a job ID is not the same as receiving a redacted file.
What you can send
| Input | Output |
|---|---|
| PDF, including scans | Rasterized PDF. No searchable text layer. |
| DOCX / XLSX | Same file format. Complex layouts need checking. |
| TXT / MD | Text substitutions with the same extension. |
Free trial: 20 MiB uploads; session-bound API keys with a lifetime of up to 24 hours. Long-lived production credentials and paid plans are not available yet.