@FireworksAI_HQ The interesting bet isn't "small beats frontier." It's whether the router + SFT stack stays cheaper after you count the human review you still need on tool calls.
@HoborgAcolyte@ItsmeAjayKV@OpenBMB Borderless tables break OCR — parsers invent lines. Markdown has no colspan; keep merges in JSON/HTML, flatten for display. If MiniCPM keeps merge positions, better than hoping Markdown can.
@testingcatalog Useful for agent loops. For one-off document jobs I still reach for free OCR APIs first — the bill only shows up when you forget the page cap.
@OpenBMB@Neywalabs The 62.9 ms median on Jev is the number I'd care about in a pipeline: cheap enough to run after every page, not only on a sample. Does Jev's score map cleanly onto "send to human" thresholds yet?
@0x0SojalSec I read the same file: deepseek-v5-next is gated behind Harness 99.0.0-alpha.1, and deepseek-v5 gets a 9-token context in that test. It's version-gating mock data, not a launch signal.
Official notes: MiniCPM-OCR 1.0 (1.3B) + Jev (2B). Runs on Apple Silicon / iPhone in their demos.
via @OpenBMB
What failure case would you send the checker first?
The underrated part of MiniCPM-OCR isn't the 1.3B parser.
It's the second model: MiniCPM-OCR Jev (2B). Its only job is grading the first one's spans and flagging shaky ones for a human.
Most OCR demos hide failures. OpenBMB shipped a checker.
@ivanfioravanti Same here, but the test that started this also gives deepseek-v5 a 9-token context window. I'd treat the names as placeholders until a changelog shows up.
@thePandaily@somarkai Before/after goes up later today — side-by-side with the PDF row count. The invented characters surprised me more than the split tables.
@geneLab_999 Got it, so a long unpunctuated run, not short clips. That fits why my 2–3s tests passed. I'll feed the same 377-char text through edge-tts Xiaoxiao and post whether it cuts.
@thePandaily@somarkai Already ran it tonight. Numbers were all correct, but the split row came back as 2 tables and it invented 2 characters. Posting the before/after tomorrow with the row count vs the PDF — will tag you.
@jiqizhixin Worth reading the actual file: it's a mock in tests/, and v5-next is gated behind Harness 99.0.0-alpha.1. It proves DeepSeek can turn on models from the server, not that V5 is close.
File (commit f3803c9):
https://t.co/Su2Bc7jG3v
What it does show: DeepSeek can switch on new models server-side and force a client upgrade.
When do you think V5 really ships?
DeepSeek V5 isn't leaking. A unit test is.
I read the file in DeepSeek's own Harness repo: deepseek-v5-next requires Harness 99.0.0-alpha.1, and another line gives deepseek-v5 a 9-token context window.
It tests version gating, not a launch. Chinese X is already counting down.
@thePandaily@somarkai Deal. I'll run it on a scanned annual report with a balance sheet that breaks mid-row, and post the before/after: raw OCR vs OXR-1.0 output, row count checked against the PDF.
@ArtificialAnlys The gap jumping 3→12 is the headline, but the same week DeepSeek Flash was #1 on OpenRouter by tokens. Would love to see an index view weighted by real usage next to the private-test score.