There is a genre of company that you can only love if you have felt the specific pain it fixes. Stedi is one of those companies. It is a healthcare clearinghouse, which is a phrase engineered to make your eyes slide off the page, so let us translate.
When your doctor's office wants to know whether your insurance will actually pay for something - the eligibility check, the claim, the remittance that says how much you owe - that information does not travel through anything you would recognize as the modern internet. It travels through EDI, a transaction standard so old it predates the web, moving as batch files over connections that would look familiar to an accountant in 1994. The clearinghouse is the middleman that shuttles these files between thousands of providers and thousands of insurers. It is invisible, it is essential, and until recently it was mostly terrible.
Stedi's proposition is almost aggressively simple: what if the clearinghouse were an API? What if a developer at a digital-health startup could check a patient's insurance eligibility with the same casual HTTP request they'd use to charge a credit card or send a text message? That is the entire pitch, and the reason it works is that nobody serious had built it. The incumbents - Change Healthcare, Availity, Waystar and the rest - grew up in the file-and-fax era and carry all of its assumptions in their bones.
The wrinkle that makes this a real business rather than a weekend project is that healthcare EDI is genuinely hard, in the way that tax software is hard: the standard is baroque, every payer implements it slightly differently, and being 95% correct is indistinguishable from being broken. Which brings us to the part of the Stedi story that is either inspiring or alarming depending on your risk tolerance.
Kanter threw away everything that had been built - every line of code - maybe eight times. It took roughly four and a half years to launch anything at all.
On building Stedi from scratch
Zack Kanter did not set out to fix healthcare. He set out to fix his own auto-parts business. Around 2011 he was bootstrapping a profitable operation, dealing with Taiwanese factories and retail partners, and the order volume got too large to key in by hand. He asked for an API. There was no API. There was EDI - the X12 standard that quietly runs retail, logistics, and supply chains - and the tooling around it was so bad that Kanter paid roughly $50,000 to have his own system built. Then he did the thing that separates a founder from a frustrated customer: he decided the tooling itself was the opportunity, sold the auto-parts business to private equity, and started a company whose name is literally EDI with an S in front of it.
Stedi began as a general-purpose B2B EDI platform. The breakout came when it aimed all of that hard-won transaction machinery at healthcare, where the pain was deepest and the willingness to pay was highest. The bet is that infrastructure this unglamorous, done this well, is extremely difficult to dislodge - because the integration work behind "3,400 payers, one API" is exactly the work nobody wants to redo.
What you can actually do with it. Verify a patient's insurance eligibility and benefits in real time or in batch. Submit professional, institutional, and dental claims - 837P, 837I, 837D - and get instant validation before they bounce. Track claim status, pull electronic remittance advice, and automate the enrollment paperwork that connects you to a payer network.
Who reaches for it. Digital-health startups, provider groups, and the EHR and revenue-cycle-management platforms that sit underneath them. Stedi's "apps" drop the clearinghouse straight into those systems, so the plumbing shows up where the billing already happens - which is the point. Good infrastructure is the kind you stop thinking about.
