One workflow.
Your choice of interface.

The website, REST API and MCP share the same document actions. This foundation is available for local development; production conversions are not enabled.

A small, predictable flow

1. List available tools.
2. Create a job with file types and sizes and a stable idempotency key.
3. Request short-lived upload URLs and transfer files directly to private storage.
4. Complete the upload and poll the job’s actual status.
5. Request a temporary download link when the result is ready.

REST API

POST /api/v1/tools/{action}
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Actions: list_tools, create_job, upload_urls, complete_upload, job_status, download, delete_job.

MCP

Connect a Streamable HTTP client to /mcp using the same scoped bearer token. The document action tool returns real states and available capabilities. No document text belongs in tool arguments.

Private by default

Keys are stored as hashes. Every job belongs to one account or browser session. Signed URLs are temporary credentials: keep them out of logs, analytics and chat history.