Stedi

For more details, check out the blog: stedi.com/blog/introduci…

Stedi now offers a free lookup tool that maps CPT and HCPCS procedure codes to Service Type Codes (STCs). CPT and HCPCS codes are used to bill for medical services on a professional or institutional claim. But most medical payers don't accept those codes in eligibility checks. Instead, payers expect an STC, a two-character code that groups services into broad categories like 'MH' (Mental Health) or 'UC' (Urgent Care). There's no standard mapping between procedure codes and STCs. Most payers don't publish theirs. This tool returns STC candidates for a given procedure code so you can test which ones a payer supports before using them in production. More details in the blog. Link below.

The guide covers when and how to use our MCP server – and tips for keeping patient data out of your agent's context. It's designed as a quick start for anyone getting up to speed when using Stedi with a coding agent. To read the guide, check out stedi.com/blog/how-to-us…

Stedi is the only healthcare clearinghouse built by design to work with coding agents, like Claude Code or OpenAI's Codex. Some clearinghouses gate their API docs. Others don't publish machine-readable OpenAPI specs. That makes it hard for agents to understand what's available, leaving them to guess at endpoints or produce code that doesn't work. We publish our docs publicly and offer machine-readable OpenAPI specs. We also publish a markdown version so you can drop them directly into your agent's context window. The best part: you can test our workflows end-to-end without real patient data. You don't need to hand an agent PHI to build with us. Our latest guide covers how to set up your coding agent for Stedi. Link below.

You can search for one-click enrollment support using the Stedi Payer Network and the Payer API. It lets you check whether a payer supports one-click enrollment before submitting a request. For more details, check out the changelog: stedi.com/changelog/optu…

Stedi now supports one-click ERA enrollment for Optum. Transaction enrollment is how a provider registers to receive specific transaction types from a payer. ERAs are the electronic reports payers send to explain how they paid a claim. Enrollment is always required for ERAs. The process varies by payer. Some require signing PDFs. Others require completing tasks in the payer's own portal. With Optum now supporting one-click enrollment, you submit the enrollment request. Stedi handles everything else. More details in the changelog. Link below.

Read the changelog: stedi.com/changelog/intr…

Stedi's ERA enrollment records now include a 'last ERA received at' timestamp. ERAs are remits, essentially receipts, that payers send to providers after processing claims to show what was paid and why. Providers can only receive ERAs through one clearinghouse at a time. If you're migrating a provider's ERA enrollments to Stedi, you can use this timestamp to track which payers have started sending remits to Stedi. You can use the timestamp to troubleshoot gaps in a payer's ERA delivery or find payers that have stopped sending remittance. More details in the changelog. Link below.

For more details on this change, check out the changelog: stedi.com/changelog/inde…

Stedi now supports one-click enrollment for Independence Blue Cross. Every medical and dental payer requires transaction enrollment for ERAs. With Stedi, you can submit transaction enrollment requests through our API, the Stedi portal, or a bulk CSV. Some payers also require extra steps, like signing a PDF, to complete enrollment. This change means you can now complete ERA enrollments for Independence Blue Cross with no forms or extra steps. More details in the changelog. Link below.

Check out the guide: stedi.com/blog/how-to-ev…

Stedi offers free production trials for evaluations and proofs of concept. If you're evaluating Stedi for eligibility checks, you can run our checks alongside those from your existing clearinghouse. After you sign up, add logic to route checks for your top 10–20 payers to Stedi. It usually takes less than 20 lines of code. You don't even need to change your payer IDs. Most teams are up and running in less than a day. Our latest guide covers the whole process. Link below.

We first began our partnership with @zackkanter and @Stedi back in 2017. Today, they announced their $50 million Series C. But most of those years were spent quietly and quite obsessively building the underlying infrastructure. Once the company built its way into healthcare, things started to inflect quickly. (They were recently named one of Ramp’s fastest-growing vendors across all categories, not just healthcare). But as with most “overnight success” stories, it was nearly a decade in the making. The ambition to replace legacy clearinghouses with a modern API-first, software-native platform is a big one, and the breadth of the product surface is stunning. But it’s Zack’s desire to keep grinding towards bigger outcomes that’s truly outlier. He’s built Stedi with unusual levels of patience and persistence. (For example, they threw away the entire codebase 8 times, and took 4+ years to launch anything publicly.) These choices stem from a determination to avoid what he calls the accumulation of not doing things the right way. His philosophy is rather unique and is best captured in this quote: “As a company, we’ve decided we’re gonna eat glass. That is what sets us apart. We’ll go to the ends of the earth to do things the right way, even when it’s not economical and it doesn’t make sense.” He gets at more of this idea in the clip below from our recent interview, where he talks about why he’s building Stedi to be a company he wants to run forever. He’s an incredibly tough founder to bet against, and I feel fortunate to both be an early supporter of his @firstround and to call him a close friend.

I'm thrilled to announce @Stedi's $50m Series C, led by Lee Fixel from Addition with participation from @Stripe, @RibbitCapital, @USV, @FirstRound, @BoxGroup, and @BloombergBeta, along with angel investors including @tobi, Charlie Songhurst, @rauchg, @karimatiyeh, @Max, and more. This latest round brings our total funding to $142 million. We’ve grown enormously over the past year. Our number of paying customers has increased by 6x year over year, and our number of billed transactions has increased by over 7x. We’re now processing more than a billion claims and eligibility transactions annually – to frame this on a relative basis, we processed more transactions in February alone than we did in the first half of 2025 combined. This month, Stedi was named one of @TryRamp's fastest-growing vendors – across all categories, not just healthcare – for the second time in ten months; we’re the first non-AI company to make the list in five months. We’ve done all this while offering a level of support that (allegedly) doesn’t scale. We offer dedicated Slack and Teams channels to every customer and now have over 1,500 shared channels. Over the past 12 months, our median support ticket response time has decreased from 18.3 minutes to just 6.7 minutes, all while handling a 6.4x increase in support volume – with 100% of tickets answered by humans. Our customers send us thousands and thousands of questions and suggestions every month, day and night, and the learnings we get from this firehose of real-time feedback are the engine that turns our business. It is this process that has made us the fastest-growing clearinghouse by a wide margin. This latest round of funding allows us to continue to accelerate development across our platform and to continue to serve customers with a first-rate support experience. One key to that is continuing to build a world-class team – to that end, we are hiring for dozens of roles across engineering, product, design, operations, GTM, and more. If building the transactional layer for the future of healthcare sounds interesting to you, drop me a note.

Changelog: stedi.com/changelog/sun-…

We now support one-click ERA transaction enrollments for Sun Life. ERA enrollments often require filling out paperwork, completing tasks in the payer's portal, or signing PDFs. This change means you can now complete ERA enrollments for Sun Life just by submitting a request. There are no follow-up steps or paperwork. More details in the changelog. Link below.

This edit applies to all claim types – 837P professional, 837D dental, and 837I institutional claims. For more details, check out the changelog: stedi.com/changelog/new-…

Stedi has a new claim edit for invalid NPIs. An NPI is the unique identifier assigned to every U.S. healthcare provider. It's always 10 digits. If a claim includes an NPI that’s too short or too long – the payer may reject the claim. That can cost the provider time in delayed payments and resubmissions. This claim edit catches the issue before the claim leaves Stedi. More details in the changelog. Link below.

For more details, check out the changelog: stedi.com/changelog/new-…

Stedi now rejects claims with a patient control number (PCN) longer than 20 characters. A PCN is a tracking ID you assign when submitting a claim. Payers return it in every acknowledgment, ERA, and status check. X12 standards – required by HIPAA – limit PCNs to 20 characters. If yours is longer, the payer may reject the claim days after submission. That delays payment for the provider. This claim edit catches the issue before the claim reaches the payer. More details in the changelog. Link below.