Document Processing
Turn PDFs and office documents into searchable, structured and automation-ready outputs.
Document processing follows the same infrastructure model as image and video: a file enters, a pipeline runs, outputs are produced, metadata is generated, and events are emitted. Ask what should be applied to the document — not who may share or retain it.
What you get
OCR & searchable PDF
Make archives searchable. Surface text from scans and born-digital PDFs for search, DAM and downstream systems.
Convert & extract
PDF and office conversion plus text, table and metadata extraction into structured, machine-readable form.
Classify, redact, archive
Classification, redaction and PII detection, plus PDF/A generation for archival-ready outputs — capability-gated where expanding.
Automation & LLM-ready
Structured JSON and normalised document transforms so workflows and models consume consistent outputs, not raw blobs.
Differentiation
Document processing on SialFlow
- OCR
- PDF conversion
- Text and metadata extraction
- Classification
- Redaction / PII detection
- PDF/A generation
- Structured output
- Automation-ready / LLM-ready document transformation
- Page-based quota and billing
- Async page workers for large documents
Example
Same auth and tenancy headers as the rest of the API. Where a capability plugs into Flows today, that is called out on the product page — we do not imply every media type shares one live pipeline yet.
POST /v1/documents/jobs
{
"source_object_id": "obj_01J8D...",
"operations": [
{ "op": "ocr", "searchable_pdf": true },
{ "op": "extract", "targets": ["text", "tables", "metadata"] },
{ "op": "classify", "model": "contracts_v2" },
{ "op": "redact_pii" },
{ "op": "normalize_for_llm", "format": "structured_json" },
{ "op": "archive", "profile": "pdf_a" }
],
"billing": { "unit": "pages" }
}Ship with Document Processing
Open the portal, follow the docs, or talk to us about rollout for your agency or commerce stack.
