| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Intelligent document processing | Data platform | 0% | 20 of 89 | 14% | 7 | under 10 labels · led by Nanonets at 32% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 1 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 1 | 0 | 1 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Choose Docparser or Parseur if you receive the exact same forms over and over again” Gemini 3.5 Flash · Document processing · budget prompt · alternative
“Docparser for the cheapest practical start on repetitive forms/documents.” GPT-5.4 mini · Document processing · budget prompt · alternative
“Fixed form layouts, lowest cost | Parseur or Docparser” Kimi K2 · Document processing · budget prompt · alternative
“Simple data extraction from PDFs/emails. | Basic parsing needs.” Grok 4.1 Fast · Document processing · budget prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“rigid rule-based parsers like Docparser” Gemini 3.5 Flash · Document processing · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 23 of the 23 answers that named Docparser and are not a share of its labels.
101 of the 101 domain citations in answers naming Docparser came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 132 | 4 | 2026-09-15 | ||
| Comparison | 16 | 0 | 2024-05-09 | ||
| Glossary or explainer | 4 | 0 | 2019-09-24 | ||
| Case study | 1 | undated |
Every page docparser.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. Read September 29, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Docparser's own pages state, read October 5, 2026: docparser.com, docparser.com/pricing, docparser.com/security, docparser.com/features, docparser.com/blog/case-studies. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Docparser's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Docparser, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Docparser by email, built from the raw record of the edition. It shows: