MXPROCESS

Asynchronous API: AI Incident Response Pack

Upload one incident report. The worker extracts embedded PDF text or OCRs a scan locally, then creates an evidence-backed incident response planning dossier. It is preparation support, not emergency response, forensic certification or legal advice.

Endpoint: POST https://mxprocess.com/api/files/start-process
Authentication: Bearer JWT from POST /api/login_check
Cost: 24 tokens, charged only after successful completion.

Start the action

curl --location --request POST 'https://mxprocess.com/api/files/start-process' \
--header 'Authorization: Bearer YOUR_TOKEN' \
--form 'file=@"/path/to/incident-report.pdf"' \
--form 'actionName="IncidentResponsePack"' \
--form 'parameters=[["language",["English"]],["organizationContext",["a SaaS company"]],["incidentType",["security incident"]]]' \
--form 'async=true'

Accepted: PDF, PNG, JPG and TIFF. Exactly one file, maximum 80 MB. Poll /api/actions/get-action-infos/{id}; outputs include source text, a Markdown situation report, timeline CSV, triage-register CSV and a downloadable JSON deliverable.

{"id":123,"action":{"actionName":"IncidentResponsePack","slug":"ai-incident-response-pack"},"accomplished":false,"trackingUrl":"https://mxprocess.com/api/actions/get-action-infos/123"}

Functional error example

{"error":"ERROR_IRP004 Incident Response Pack accepts PDF, PNG, JPG and TIFF files only."}

For short documents use the synchronous API.