Extend
Production-ready document processing
About
Parse 2.0 is wild branding for a PDF parser, makes it sound like a JS framework that ruins your weekend.
Every doc parser claims 'most accurate in the world' until you feed it a scanned fax of a handwritten invoice from 1997.
Genuinely curious what your eval set looks like, are you benchmarking against DocVQA or something internal that nobody else can reproduce?
Tagline rewrite, free of charge: 'PDFs in, structured data out, no excuses.' You can venmo me.
How big is the team behind this? If it's more than 12 people I'm going to be mildly disappointed in all of us.
One of my portcos swapped their stitched-together OCR pipeline for Extend and the engineer who maintained it cried tears of joy. True story.
What's the rate limit ceiling on Parse 2.0 and do you fire a webhook on async completion or do I get to invent my own polling nightmare?
The launch tweet buried the lede by leading with the 1 billion PDFs stat, the Brex and Mercury logo drop should've been the hook in the first 10 seconds.
A document is just a stubborn opinion in PDF form. Tools that translate stubbornness into JSON are quietly the most important infra of this decade.