Skip to main content

Overview

The Extract pipeline is the simplest and most common way to use Pulse. Upload a document and get back clean, layout-aware markdown along with extracted tables, figures, bounding boxes, and optional chunks. This is the starting point for every other pipeline — Extract → Schema and Extract → Split → Schema both build on top of this step.

When to Use

  • RAG ingestion — feed clean markdown into a vector database
  • Search indexing — convert documents to searchable text
  • Content migration — pull content out of PDFs into your CMS
  • Table extraction — grab structured tables from financial reports, invoices, or spreadsheets
  • General-purpose parsing — convert any supported file type to machine-readable text

Supported File Types

Pulse handles a wide range of document formats out of the box:
For the full breakdown including processing tips per format, see Supported File Types.

How to Use in the Playground


What You Get Back

The extraction_id is the key to the rest of the Pulse pipeline. Once you have it, you can run Schema or Split on the same extraction without re-processing the document.

API Usage

For large documents, use async mode and poll for results:
See Async Processing for the full polling flow.

After Extraction

Once you have your extraction_id, you can:

Add Schema

Extract structured data fields with a JSON Schema

Split & Schema

Divide into sections and extract per-section structured data

Tables

Extract structured tables with span detection and cross-page merging

Extract API Reference

Full API documentation for the /extract endpoint

Supported File Types

Detailed breakdown of every supported format