Re:Benchmarking the Most Reliable Document Parsing API
by coderintherye on Thursday November 06, 2025 @02:36PM
(#45839320)
Google's Vertex API for document processing absolutely does bounding boxes. In fact, some of the document processors are just a wrap around Google's product.
Re:Benchmarking the Most Reliable Document Parsing API
by diptanu on Thursday November 06, 2025 @02:48PM
(#45839489)
OP mentioned Gemini and not Google’s Vertex OCR API which has very different performance and accuracy characteristics than Gemini
Re:Benchmarking the Most Reliable Document Parsing API
by ianhawes on Thursday November 06, 2025 @02:30PM
(#45839252)
I just tested a non-English document and it rendered English text. Does your model not support anything other than English?
On Gemini and other VLMs - we excluded these models because they don't do visual grounding - aka they don't provide page layouts, bounding boxes of elements on the pages. This is a table stakes feature for use-cases customers are building with Tensorlake. It wouldn't be possible to build citations without bounding boxes.
On pricing - we are probably the only company offer a pure on-demand pricing without any tiers. With Tensorlake, you can get back markdown from every page, summaries of figures, tables and charts, structured data, page classification, etc - in ONE api call. This means we are running a bunch of different models under the hood. If you add up the token count, and complexity of infrastructure to build a complex pipeline around Gemini, and other OCR/Layout detection model I bet the price you would end up with won't be any cheaper than what we provide :) Plus doing this at scale is very very complex - it requires building a lot of sophisticated infrastructure - another source of cost behind modern Document Ingestion services.