One endpoint, five stages, zero parsers on your side.

1. fetch

   Ingest

   POST the bytes directly (multipart or base64), or pass a URL and txtfetch fetches the document server-side — handy for links your users paste and files already sitting on a CDN.

2. detect

   Detect

   Content-type sniffing on the actual bytes, not the file extension. A .pdf that's really a scanned TIFF in a trench coat still comes out as text.

3. extract

   Extract

   Apache Tika parses the document structurally — body text, tables, slide notes, email bodies and attachments — and normalizes the result to clean UTF-8 plain text.

4. ocr

   OCR fallback

   When a page has no text layer — scans, faxes, screenshots, photographed receipts — Tesseract OCR takes over automatically. You don't opt in; it's just what happens when pixels arrive.

5. respond

   Respond & forget

   You get JSON with the extracted text and basic metadata. The document itself is processed in memory and discarded — we meter requests, never store content.

under-the-hood

Boring technology, deliberately.

txtfetch doesn't reinvent extraction — it operationalizes the best open-source tools ever built for it. Apache Tika has spent two decades learning every format's dialects and corruptions; Tesseract is the OCR engine everything else is measured against. We run them serverless, keep them patched, scale them to your traffic, and wrap them in an API you can integrate in five minutes.

Your documents stay yours: processed in memory, never written to storage, never used for anything but your response.

Tika's structural recovery holds up well on Office docs, HTML, and email — it's hard PDFs (multi-column layouts, scans, wide tables) where a premium VLM tier closes a real accuracy gap. See the measured numbers on the benchmarks page.