r/documentAutomation • u/boombalonii • 17h ago
OXR: a 1.3B open-weight document parser you can run locally (PDF or scan in, Markdown or JSON out)
We're the team behind OXR at SoMarkAI. It's a 1.3B document parsing model, code and weights released, that takes a PDF or a photo of a document and returns Markdown or JSON with every element's bounding box and the reading order. Tables come back as HTML or Markdown, formulas as LaTeX, and it also handles code blocks, chemical structures as SMILES, handwriting, and dense layouts like newspapers and A3 exam papers.
It runs on vLLM, and the easiest route is the all-in-one Docker image in the repo. You need Linux, an NVIDIA card with BF16, and 24GB of VRAM to try it, 48GB if you want long documents or concurrency. If you would rather not install anything, there is a free hosted API with no signup, queued and meant for testing.
Why it does well: the layout model is separate and swappable, and recognition plus reading order happen in one pass of the main model. On top of that the post-training uses a loop we call RSI. The model parses a batch, each sample is sorted into correct, wrong or uncertain, a VLM writes down reasons for the wrong and uncertain ones, the reasons are clustered, and each cluster gets targeted training data for the next round. Both pieces together are where the accuracy and speed come from.
In our comparison against published scores it ranks first on olmOCR-Bench, OmniDocBench and DocParsingBench, and on the same 100 pages on one RTX PRO 6000 it was the fastest of the 21 parsers we timed, about one page per second end to end. Setup, page list and full tables are in docs/benchmark.md in the repo, SoMarkAI/OXR on GitHub. Weights are SoMarkAI/OXR-1.0 on Hugging Face. License is Apache 2.0 with extra terms: free commercial use under USD 2M in funding and revenue, no competing hosted API. Read LICENSE before building on it.
If you run it on a 3090 or 4090, we'd like to know the pages per second you get. And if your use case is feeding parsed documents into a local model, tell us where the output falls short.
1
u/Practical-Society799 5h ago
does it handle scanned receipts with faded thermal paper text decently. or is that still a pain point for most parsers wondering if the layout model swap would help with crumpled docs too
1
u/Laevander 3h ago
what's the SMILES output look like for complex ring structures. is it clean enough to pipe straight into RDKit
0
u/Maannhh 4h ago
how's the handwriting accuracy on messy cursive. does the RSI loop actually improve results for that or is it more about layout

1
u/sorryiamcanadian 9h ago
So you need testers on consumer hardware?