A 2B model that grades OCR: MiniCPM-OCR, 10 days, 823 stars. A big-company release, and here's which half you can learn

Shanghai-based Mianbi Intelligence and OpenBMB open-sourced two models in October 27: a 1.3B document OCR model, and a 2B model called Jev that specifically grades whether OCR results are right. The repo got 823 stars in 10 days (GitHub, 11-06), and the whole family totals about 150k downloads on Hugging Face. The stars mostly came from OpenBMB's brand, with its 170k stars, and a full launch playbook that individual developers can't borrow. But the idea of not competing on accuracy in a crowded space and building a verifier instead, along with the release rhythm, is something anyone can learn. Below: what it is, where the stars came from, who grew faster in the same period, and where you should start.

A post asking "is your OCR really right?"

On Oct 2026 27 16:52 (UTC, which is 28 early morning Beijing time), @OpenBMB posted the launch on X. The first line wasn't "SOTA" but a question:

Your OCR says it's done—but did it get everything right? In high-stakes workflows, even a small error can be costly.

(Your OCR says it's done, but is it really all correct? In a process that matters, one small error can be very costly.)

Here are the parameters: the 1.3B MiniCPM-OCR scores 93.68 on Real5-OmniDocBench 1.0. The 2B Jev is "a sharp goalkeeper": it checks the text, formulas and tables produced by different OCR parsers, and scores an AUROC of 93.6 on JevOCRBench. That beats the 35B JEV-35B-A3B (90.1) and comes close to Qwen3.5-397B (93.8). The post also lists a string of day-0 partners: Arm, Intel, NVIDIA and Moore Threads, plus 10 more chip vendors that connect through FlagOS. vLLM, SGLang, llama.cpp and Ollama are all usable on day one.

The next day, AI blogger @omarsar0, with 326k followers, reposted it with a point that wasn't about how accurate OCR is, but that "decision models can also improve your OCR pipelines." That post got 133 likes and 9,300 views, the biggest single post about it on X. Almost every news headline picked up the same angle: it will "flag its own mistakes."

What it actually is

Two models plus a set of ready-to-use tools, all under Apache-2.0. Code, docs, and weights are all licensed for commercial use.

• MiniCPM-OCR 1.0 (1.3B): converts Chinese and English documents and PDFs into Markdown or JSON, recognizing text, tables, formulas, charts, and seals, and can extract key information. It handles scans, photos, curved pages, and re-photographed pages. The official claim is that with DSpark speculative decoding, its throughput is 1.49 times that of Baidu's PaddleOCR-VL-1.6 and 3.62 times that of MinerU2.5 Pro. These are self-reported numbers; an evaluation site noted the model card is inconsistent, mixing 1B and 1.3B, and 93.68 and 93.75.
• MiniCPM-OCR Jev (2B): give it an image of a region and an OCR result, and it returns a score from 0 to 1, meaning "is this recognition right or not." High scores pass through; low scores go to a human. The key is that it doesn't depend on the upstream tool: outputs from GLM-OCR, PaddleOCR-VL, and Xiaomi's OCR can all be scored. The README has a chart showing the trade-off between "auto-pass rate" and accuracy across legal documents, financial receipts, and complex documents, with a reminder below: test thresholds on a small batch of real business data before setting them.
• Tools: a pip SDK, a free API, an online demo, and a SKILL.md for coding agents (the README says to send your agent this line: Read and execute …SKILL_jev_en.md). Later came an open-source web demo, offline iPhone support, and a Docker image.

In plain terms: the first model does the reading, and the second model grades the work. The first is the Nth "yet another SOTA OCR." The second is the new thing.

Where the stars came from

Source: GitHub daily star counts. A typical launch spike: 600 stars in the first three days, then only 10 to 30 per day from day five on.

Almost all the traffic came from official organizations:

• Official accounts cross-posted: X, the Mianbi WeChat account, Zhihu column, ModelScope, and a PR Newswire release on Oct 31.
• Ecosystem partners published the same day: Intel OpenVINO published "Day 0: MiniCPM-OCR is now available on Intel Hardware" on Medium on Oct 27. MLX, the official Ollama library, and llama.cpp were usable on day one. People who run models locally could use it right away, and the gguf version got 39k downloads on Hugging Face.
• AI news sites reposted in bulk: over twenty articles from Oct 27 to Nov 4, many of which look auto-generated. Reddit's r/LocalLLaMA had at least 3 posts (engagement not checked). Hacker News had none.
• An update every two or three days: the web demo, iOS, and Docker came out one after another, each with a news site writing it up, which stretched out the tail of the launch spike.

A downside: the launch announcement was also written into the README of the older repo MiniCPM-V, which has 27k stars, so some stars were diverted. In the same period the old repo gained only about 80 stars, and the new repo never made the GitHub trending chart. To push a new repo onto the charts, concentrate traffic on one place.

Others grew faster in the same period

Placed against the wave of small OCR model launches in late October, 823 stars only ranks mid-table:

Numbers from GitHub and Hugging Face, 11-06. The most worth looking at is OXR: no big-tech brand, only competing on parsing accuracy, with more than 4 times MiniCPM-OCR's stars. It shows stars in this space don't fully follow brand, but it also shows that "yet another OCR model" is already crowded, and MiniCPM-OCR's own layout detection still uses Baidu's PP-DocLayoutV3.

The truly empty slot is Jev's. The "judges" the official side compares against are all general-purpose LLMs of 35B and 397B; we found no other open-source small model dedicated to judging whether OCR output is correct (ModelBest calls it "the industry's first OCR discriminator model"; not independently verified).

There's also a name-piggybacking site: minicpmocr.com, titled "MiniCPM OCR — Image & PDF to Text", charging per page ($3 / 100 pages, Pro annual $190, "launch 50% off"), with an FAQ saying "OCR is processed by ModelBest". It looks like a third-party wrapper on ModelBest's API that uses the model name for search traffic; the operator was not found. This is common around LLM launches, but it's not the same thing as open-source stars.

If it were you

C: Learn its approach and release rhythm, don't try to compete with the model. Training an OCR model takes compute, data, and a team; its stars mainly come from the OpenBMB brand, day-one support from a dozen chip and framework vendors, press releases and big accounts reposting, none of which individual developers can get. And even if you did, you'd only end up with mid-table results at 823 stars.

Who it's for: developers building document processing, RAG, or data-cleaning tools who already have a pipeline that needs OCR; or people good at developer tools who can stitch several models into something actually usable.

Who it's not for: solo builders who want to train a "more accurate small OCR model" to top leaderboards; people who want to build yet another general PDF-to-Markdown tool in the OCR space (MinerU, docling, and marker already hold that ground).

How to do it: build the layer it didn't. Jev and a pile of new OCR models are all free, commercially usable, locally runnable parts, but no one has yet assembled them into something developers can use out of the box. A few concrete directions: ① a "multi-OCR router": run two or three models on the same page at once, use Jev to pick the highest-scoring output per region, and put a table in the README showing "stitched together beats any single model"; ② a human review interface: only highlight low-scoring regions for a person to fix, then export the corrected data ready for fine-tuning; ③ apply the "verifier" idea elsewhere: build a lightweight judge model or rule layer for speech transcription, table extraction, or invoice fields. The lighter the form the better: one command to run, with a built-in Skill file so agents can install it directly.

How to get users: copy its rhythm, not its scale. On launch day, get local run options like Ollama and llama.cpp set up, and put a comparison chart that gets screenshotted and shared on the first screen of the README; post on r/LocalLLaMA and X with a title describing the problem you solve ("which OCR regions need a human to look"), not the parameters; then ship a small update every two or three days, each one another round of exposure. Don't scatter announcements across several repos; concentrate traffic in one.

When to get in early: this wave of small-OCR-model releases started in late October; discussion heat probably has a month or two left (inference). Assembly-type tools should ship before the end of 2026, while people are still comparing "which OCR is best".

What would mean I got it wrong: ① ModelBest or another big player releases an official "multi-model router + review interface" tool, and that layer gets taken; ② before year-end, Jev's downloads on Hugging Face stall at 20–30k with almost no one mentioning it in other projects, showing that "OCR quality control" isn't as big a developer need as it seemed; ③ a backgroundless assembly project passes 2,000 stars within a month, which means the direction is right but the open slot has already been taken.