PCO

pco drives a Mathpix Private Cloud OCR deployment running in your own
infrastructure. It speaks the same document API as scs, plus the deployment-only endpoints
for jobs over a cloud folder, status, and usage.

Point --endpoint at your deployment. A deployment usually needs no credentials of its own; pass
--token or the client-certificate flags if your ingress requires them. Set the endpoint once with
mpx configure (or MPX_ENDPOINT) to avoid repeating it.

mpx pco --endpoint http://pco.internal:8080 convert paper.pdf paper.mmd --formats docx
mpx pco --endpoint http://pco.internal:8080 convert ./scans/ ./out/ --formats md
mpx pco --endpoint http://pco.internal:8080 convert s3://acme-docs/scans/ --formats md

A file or a local folder is sent to the deployment and the outputs are written locally. A cloud
folder (s3://, gs://, or an Azure blob URL) becomes a server-side job over the deployment’s own
storage; the outputs land in your bucket. Every converted document yields mmd and lines.json;
--formats adds conversion formats on top. A single image is OCR’d through the deployment’s
synchronous /v3/text automatically.

mpx pco --endpoint http://pco.internal:8080 status     # versions, workers, license and metering
mpx pco --endpoint http://pco.internal:8080 usage --from 2026-09-01 --to 2026-09-30
mpx pco --endpoint http://pco.internal:8080 usage --export   # signed statement for an airgapped deployment

Manage server-side batch jobs over a folder in your bucket:

mpx pco --endpoint http://pco.internal:8080 jobs list
mpx pco --endpoint http://pco.internal:8080 jobs get JOB_ID
mpx pco --endpoint http://pco.internal:8080 jobs files JOB_ID --status error
mpx pco --endpoint http://pco.internal:8080 jobs report JOB_ID
mpx pco --endpoint http://pco.internal:8080 jobs retry JOB_ID
mpx pco --endpoint http://pco.internal:8080 jobs cancel JOB_ID

Transport flags on the pco service, layered on top of the global app_id / app_key:

Every command has --help for its full set of flags.