A wall of text your pipeline has to clean up later.
- ×Multi-column paragraphs arrive in the wrong reading order.
- ×Tables collapse into strings and headings lose hierarchy.
- ×No page, box, parser, or confidence metadata for debugging.
Document parsing API
Turn PDFs, scans, slides, spreadsheets, and images into Markdown and DocIR JSON for search, RAG, automation, and agents.
20 documents free · deterministic parsing · 200 MB · no card requiredFY25 report12
Platform revenue rose to $82 million, mostly from seats added in the second half.
Services stayed near $41 million. Renewals covered the work that did not grow.
| Segment | FY25 | Change |
|---|---|---|
| Platform | $82M | +31% |
| Services | $41M | +12% |
A flat text extract drops tables, reading order, page boundaries, and the warnings you need when a result is wrong. DocParse keeps that structure on the parsed record.
The files are already on the customer side. The product needs headings, tables, page numbers, and a route you can inspect.
Preserve headings, tables, page references, and reading order before chunking and embedding.
Chunk by heading and pageAccept PDF, Office, HTML, XML, CSV, and images through one API.
Skip a separate parser per formatNormalize uploaded files before classification, review, extraction, routing, or human approval.
One record per uploaded fileTurn mixed-format repositories into consistent, traceable artifacts for indexing and migration.
Index pages, blocks, and source idsRoute from the file
Digital PDFs take a deterministic text-layer path. Scans and complex layouts can use OCR or layout vision. Office files keep their native structure. You get one API and a traceable route decision.
The free Trial validates deterministic parsing first. Image, Fast AI, and Layout-aware processing are enabled only for approved paid workspaces.
Use inline parsing for normal files or jobs, queues, retries, cancellation, and webhooks for slower work.
Inspect routes, job events, warnings, parser versions, manifests, and tenant-scoped artifacts.
External OCR is explicit and tenant-controlled. URL imports and webhooks can be restricted by host.
Send a file to one authenticated endpoint and receive clean Markdown plus layout-aware DocIR JSON. Start inline, then move the same integration to async jobs and webhooks as volume grows.
Open a free workspace, name the key for your backend, and copy the secret once.
Upload multipart or raw binary, or import a permitted HTTPS URL.
Read result.markdown for RAG and result.document when layout, blocks, and provenance matter.
# Keep the key in your backend environment
export DOCPARSE_API_KEY="your_key"
# Parse now and save the complete response
curl -X POST "https://docparse.genedai.me/v1/parse?wait=true" \
-H "Authorization: Bearer $DOCPARSE_API_KEY" \
-F "file=@document.pdf" \
-F "mode=both" \
-o result.json
# Send Markdown to retrieval; keep DocIR for structure
jq -r '.result.markdown' result.json > document.md
jq '.result.document' result.json > document.docir.json
Add ?wait=true for normal files and receive the job, Markdown, DocIR, and manifest together.
Remove ?wait=true, then poll the result link or receive a terminal webhook.
Use scoped keys, quotas, idempotency, cancellation, artifact purge, and tenant-specific URL policies.
A workspace can revoke a key, cap monthly jobs and bytes, and delete retained files without guessing what the parser stored.
Hashed API keys, explicit scopes, revocation, monthly quotas, and concurrent job admission.
Idempotency keys, retries, dead-letter handling, cancellation, purge, and signed webhooks.
Original clean-room parsing code, permissive dependencies, and Apache-2.0 project licensing.
05 / Learn before you integrate
Outputs, routes, lifecycle, access, cost, and retention in one product system.
Explore product →Architectures for RAG, AI agents, knowledge bases, search, and automation.
Choose a use case →Direct comparisons, best-tool maps, and migration alternatives grounded in official documentation.
Definitions, scanned PDFs, PDF to JSON, RAG ingestion, routing, and retention.
The free workspace covers 20 text-based documents and 200 MB per month. Trial parsing is deterministic. Read the Markdown and DocIR before you rebuild the pipeline around it.
20 documents · 200 MB
Deterministic parsing · no payment card