Process PDFs

capout_process_pdf is the primary MCP tool for single-document processing.

Required arguments

Send exactly one of:
- pdf
- url
- file_base64
- file_path
When using file_base64, also send file_name

When using file_base64, keep the PDF at or below 50 MiB. xn_address and profile_code are optional, deprecated compatibility inputs. New MCP calls should omit them. CapOut generates both Contractor (8D) and Carrier (5L) files for every successful workflow. For local or workspace PDFs on a hosted MCP, use Staged Uploads, which supports PDFs up to 50 MiB. For the public CapOut MCP, the practical inputs are pdf, url, and file_base64. The MCP is hosted remotely and cannot read your local machine paths directly.

Use the right source type

Use pdf for ChatGPT-style file attachments that include download_url and file_id
Use url for a public https:// PDF URL
Use file_base64 when the client has bytes but not a URL and the inline payload stays within the 50 MiB limit
Use file_path only for a path that already exists on the CapOut MCP server itself. Do not send your local /Users/... or workspace path here.

CapOut MCP is hosted remotely and cannot read your local filesystem. For local workspace PDFs, use Staged Uploads.

Example: attached PDF

{
  "tool": "capout_process_pdf",
  "arguments": {
    "pdf": {
      "download_url": "https://files.chatgpt.com/file-123",
      "file_id": "file-123"
    }
  }
}

Example: HTTPS PDF URL

{
  "tool": "capout_process_pdf",
  "arguments": {
    "url": "https://example.com/claims/123/estimate.pdf"
  }
}

Example: inline base64

{
  "tool": "capout_process_pdf",
  "arguments": {
    "file_base64": "JVBERi0xLjQKJ...",
    "file_name": "claim-123-estimate.pdf"
  }
}

Successful response

The MCP returns the document handoff plus stable links that can be saved immediately:

{
  "document_id": "b9cf4ef8-9fa3-441b-b0d3-990bee7fbcce",
  "download_url": "https://api.capout.ai/b9cf4ef8-9fa3-441b-b0d3-990bee7fbcce.esx",
  "contractor_download_url": "https://api.capout.ai/b9cf4ef8-9fa3-441b-b0d3-990bee7fbcce.esx?profile=contractor",
  "carrier_download_url": "https://api.capout.ai/b9cf4ef8-9fa3-441b-b0d3-990bee7fbcce.esx?profile=carrier",
  "download_authentication": "Send your CapOut API key in the capout-api-key header when requesting an ESX URL. Never put the key in the URL or query string.",
  "message": "CapOut accepted the document for background processing. Keep polling until terminal is true; the download links return 409 until export completes."
}

The returned download_url is the default Contractor link. The URLs stay stable and refresh their private S3 signature after an authenticated request. The key must belong to the document’s organization.

What to do next

After the document is accepted, keep polling until the export reaches a terminal state:

When the status tool reports success, return download_url and carrier_download_url with the capout-api-key header requirement. Do not put the key in a URL, and do not return or retain the redirected S3 URL.

Get Started

Workflows

MCP

Required arguments

Use the right source type

Example: attached PDF

Example: HTTPS PDF URL

Example: inline base64

Successful response

What to do next

​Required arguments

​Use the right source type

​Example: attached PDF

​Example: HTTPS PDF URL

​Example: inline base64

​Successful response

​What to do next

Required arguments

Use the right source type

Example: attached PDF

Example: HTTPS PDF URL

Example: inline base64

Successful response

What to do next