Visitar URL original
Unstructured Transform: Document Parsing API & MCP for AI Agents | Unstructured
Unstructured Transform

Agentic document extraction for your most complex files

Unstructured Transform turns PDFs, Word and PowerPoint files, scans and images into clean Markdown or structured fields. Send a document to the API and Transform decides how to read it, so there are no models or pipelines to tune.

Ranked #1

Table Accuracy

Extracts complex tables without losing structure.

Ranked #1

Content Accuracy

Preserves your documents as they were written.

Ranked #1

Lowest Hallucination Rate

Keeps extracted content grounded in the source.

Documents in, structured data out.

Every document needs a different approach. Transform decides how to read each one, then returns clean Markdown or typed elements with page numbers and positions you can cite back to.

Works with

Built for the
hard files.

Filled forms come back as fields, with handwriting and checkbox states intact. Scans with no text layer come back as clean text. Dense tables keep every row and column, even across page breaks.

How Transform works

No pipeline to configure. No AI provider to set up. No models or prompts to tune. Try it on your own files, then click Get Code for working Python, TypeScript or cURL.


  1. STEP 01

    You send.

    Upload a PDF, Word or PowerPoint file, scan or image in the web app, or send it to the API in seven lines of code.


  2. STEP 02

    Transform decides.

    It chooses what runs on each document, scanned or born-digital, using models we fine-tune specifically for document work.


  3. STEP 03

    Files are done.

    Get clean Markdown, typed elements with page positions, or just the fields you ask for, ready for your database, search index or LLM.


Transform MCP

Use Cases

Structured Data Extraction

“Extract all invoice numbers from this PDF.” ”Collect all term dates from this contract.” “List every payment term in this doc.”

RAG

“Get this document RAG-ready.” “Chunk these files for semantic search.” “Prepare this PDF for embeddings.”

Agents

“Add these docs to my second brain." "Analyze these PDFs and build a report." "Research this topic across all these files."

Automation

“Turn this folder into structured data.” “Extract invoice data into a spreadsheet.” “Index these files for search.”

Transform MCP

Start today.

Upload your own documents and see the results for yourself. Your first 10,000 pages are free, no card required.

FAQs

Answers to our most common questions around Transform.

Vision can get you the PDF. It doesn't get you the spreadsheet, the deck, the scanned contract, or the 9 other formats sitting in a real corpus. Unstructured Transform reads all of them and hands your agent structured data back, so it's not limited to the handful of file types the model can open on its own. Think giving your Claude a special pair of glasses 😉

You can, and plenty of people start with the open-source library. What you're paying for is not building and babysitting the pipeline around it: strategy per file, scans versus clean text versus tables, growing format support, support at scale, our latest parsing techniques as we release them, and more. If you'd rather own all that, OSS is the honest answer.

Here’s some examples. RAG pipelines: parse, chunk, and embed documents into a vector store. Semantic memory: turn a whole corpus into embeddings your agent can search back to later. Structured data extraction: pull specific fields into JSON against a schema you define, like vendor and total off of an invoice all without you having to become a document processing expert yourself. The (unstructured data) world is your oyster.

10,000 pages a month free, then $0.015 cents a page after that. And since the parsing runs on Transform's side rather than in your model's context, you're not burning context tokens to do the extraction yourself.

Different jobs. Unstructured Transform parses files you point at right now; Foundation gives your agents standing access to your whole corpus across sessions. If your problem is "my agent just hit a document and needs to read it properly," that's Unstructured Transform.

Nope. Your agent comes up with the best strategy based on instructions it has from the tool, but you can also override it in plain language: force hi-res or VLM, table enrichments, set chunking, embedding, and output formats. The agent is just choosing what it thinks is the best path.

That's what it's for: 9 file types including scans, images, spreadsheets, slide decks, and PDFs with charts or margin handwriting. Tables come back structured, layout survives, and our partitioner also handles your worst handwriting.