The interesting engineering in Parse 5 is where the vision features land. Cohere injects patch embeddings from several layers of the vision encoder into the early layers of the language model, an approach it calls DeepStack [7]. Early layers matter, because the decoder is conditioned on visual detail before it has settled on a linguistic reading of the page. The encoder is a 400M-parameter native-resolution model initialised from SigLIP 2 SO400M, carrying 2D rotary positional embeddings plus learned 1D embeddings so the page's spatial structure survives the trip [4]. A table is geometry before it is language, and that positional scheme is the part doing that work. A separate projector maps the features into the language model's embedding space [5], and the reasoning engine is a 2B in-house model built on Cohere's Command A+ architecture [6].
Add the published parts and you get 2.4B against a headline 2.3B [1]. The report does not reconcile the two, which is a reminder to treat a parameter count in a launch post as a claim rather than a sum.
The number I would check before anything else is the context window: 8K tokens, shared by text and visual inputs in the same request [2]. InfoQ does not say how many pages fit inside it [6]. So a long filing goes through page by page, and anything crossing a boundary, a table continuing overleaf or a footnote resolved later, gets stitched by your code. High volume is exactly the workload where that stitching becomes the cost, and Cohere pitches this model at high volume [2].
ParseBench is Cohere's own harness: over 2000 human-verified enterprise pages from insurance, finance and government, scored by rules on table extraction, content faithfulness and semantic formatting [9]. Parse 5 averages 79.2 there [10]. LlamaParse Agentic Plus, which InfoQ describes as a premium configuration, leads the leaderboard at 90.20 [11], eleven points clear [2]. Parse 5 sits 4.15 points above the 75.05 that InfoQ reports for the group it names, Mistral OCR and Google Gemini 3 Flash (Thinking High) [12][3]; the write-up does not break that number out per system [12], so read it as one line in someone else's table. The 79.2 transfers to your pipeline only if your pages resemble those three sectors and if the rule-based scorer's idea of correct Markdown matches what your chunker downstream actually consumes.
Evaluation is cheaper here than with most proprietary launches. parse-v5.0 is proprietary, but the base North-Micro-Vision-Instruct architecture is open-weight on Hugging Face [3][15], so the architecture can be run against your own documents before anyone signs anything. Endpoints on Microsoft Azure AI Foundry and Amazon SageMaker matter for buyers who cannot post documents to a vendor API [14]. The call surface is one method, co.models.parse with output_format set to markdown, and the layout coordinates come back on response.bounding_boxes in the same response [16]. That second field is what makes the first defensible when a reviewer asks where a figure came from [13]. If your stack today is pypdf with a Mistral OCR fallback, as one r/Rag commenter described theirs [17], table extraction is the dimension worth isolating from the average.
