DocuPipe

Tools

• Create Schema

  Create a reusable extraction schema from a valid JSON Schema and optional extraction guidelines.

• Delete Document

  destructive

  Permanently delete one previously submitted DocuPipe document by ID. This destructive operation cannot be undone.

• Delete Documents

  destructive

  Permanently delete multiple previously submitted DocuPipe documents by ID in one batch. This destructive operation cannot be undone.

• Find Documents

  Browse documents by dataset and creation time, or search filenames and document IDs when query is provided. Returns one page and a continuation cursor.

• Find Jobs

  Retrieve one asynchronous job by ID, or list and filter jobs when job_id is omitted. Job details expose status, progress, errors, outputs, and credit use.

• Get Account Usage

  Return current plan and credit state together with job counts and credits consumed by job type, optionally including daily usage.

• Get Document

  Retrieve a processed document, including processing state, parsed content, page count, metadata, and file details.

• Get Schema

  Retrieve one extraction schema and its full JSON Schema definition by ID.

• Get Standardization

  Retrieve one completed standardization as structured JSON, including extraction data and field metadata.

• List Schemas

  List extraction schemas available to the connected workspace, optionally including each full JSON Schema payload. Returns one page and an opaque continuation cursor.

• List Standardizations

  List structured extraction results, filtered by schema, document, or up to 1000 known standardization IDs. Returns one page and a continuation cursor.

• Standardize Document

  Start V3 agentic structured extraction for one processed document and return the job and standardization IDs. Standard effort costs 2 credits per page; high effort costs 4 credits per page. Omitting schema_id also consumes schema-generation

• Upload Document

  Submit one local file or remote file URL for asynchronous parsing. Returns the document and job IDs used to track processing. When workflow_id is provided, also run that existing workflow after parsing and return its result IDs. Processing

Works well with

How Switchy teams use it

Starter prompts

More docs MCPs

• DocuPostDocuPost
• DocuPotionDocuPotion
• DraftableDraftable
• Eagle docEagle doc
• EchtpostEchtpost
• Eledo PDFEledo PDF
• EncodianEncodian
• EvernoteEvernote
• Extracta.aiExtracta.ai
• FileToPDF.devFileToPDF.dev
• Google DocsGoogle Docs
• Google DocsGoogle Docs

See all docs MCPs →