HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
eigenpal
openparser
TypeScript2026–2026
eigenpal / openparser

openparser

OpenParser schema, adapters, SDKs, and CLI

2Distinct people
3Mentions
0Explicit recommenders
12GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

OpenParser schema, adapters, SDKs, and CLI

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2026-07-29 15:20:59 UTC to 2026-09-15 19:27:34 UTC. Weeks start Monday, UTC.

012026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 272026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 172026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 14

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC110
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC110
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC000
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC101

What Hacker News says

3 sources
If you've ever extracted json data from files using llms, you know the pain in deciding if you can trust it or not. We found a solution that works well for our users: we track the full lineage of every extracted filed from the source document to the structured output. Our approach takes into consideration ocr (parsing), extraction and transformations steps. Results come with confidences attached, so you know which fields need a double check and approval from a human. And this human-in-the-loop mechanism, where humans only check low confidence results,. can be used effectively to speed up existing backoffice operations that deal with document workflows. You can try it right now at openparser.dev , or read this (https://www.openparser.dev/blog/how-openparser-uses-lineage) on how we built it and why one-shotting an llm to extract data from
Read the rest
documents simply didn't work for us and our users. oh and if you want to build with full lineage yourself, we opensourced it: https://github.com/eigenpal/openparser/tree/main/packages/li...
In [dead]
nmatej1·Aug 10, 2026Submission

Show HN: OpenParser – swappable OCR models in one API

We build document AI workflows, and OCR is finicky. At scale, it becomes hard to debug errors and compare confidence scores across providers. New OCR models appear all the time, so we wanted one interface that lets us swap models in and out without rewriting around each provider. So far, we’ve integrated nine models from PaddleOCR, Mistral, Azure, Google and AWS Textract. We run them at cost, with no markup. We also created and open-sourced a shared schema, openparser@1, plus adapters that normalize each provider’s response. You can switch OCR models without changing the rest of your application: https://github.com/eigenpal/openparser I’d appreciate feedback on the schema and which models or providers we should add next.
2 points · Open discussion

Show HN: Parse a PDF from your terminal with PaddleOCR-VL-1.6

I built OpenParser because I wanted PaddleOCR-VL-1.6 behind an endpoint I could actually use. Now there are open-sourced CLI and TypeScript/Python SDKs: ``` npm install -g @openparser/cli openparser auth login openparser parse sync document.pdf ``` That is basically it. It doesnt get easier and cheaper that this. Give it a PDF and get back the text and document structure. Repo: https://github.com/eigenpal/openparser I would love feedback from anyone willing to try the CLI and tell me what is still annoying.
7 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.