Primary source: Availity, November 16, 2026, Jacksonville, Fla.
On November 16, 2026, Availity launched Availity Extend. A provider or a technology company can reach the Availity network from its own applications, automation platforms, and customer-managed AI agents through REST APIs, a sandbox, and Model Context Protocol tooling. If you run revenue cycle, that is coverage, patient estimates, claim status, remittance, and prior authorization offered as governed tools, next to the payer portal and the EDI you already send. Availity unveiled Extend on April 28 and said broader availability would come later in 2026. This is that launch, and it is the first release that names MCP. The 126 claims in 30 seconds are one test Availity reported.
Availity says MSN Healthcare Solutions, an early adopter, built a claim-status automation in a few hours with AI-assisted coding. In one test it checked 126 claims in 30 seconds. Availity says the same work previously took at least six hours, at 5–11 minutes on hold and three claims per call. Availity is demoing at HLTH, booth 5054, in the AI Zone.
Availity’s line is that connectivity already existed, and Extend “activates” it. Healthcare technology companies, developers, and provider organizations get the network through one secure integration instead of treating eligibility, estimates, claim status, claims editing, and submission as separate manual steps. Availity says Extend manages the connectivity, security, governance, and enrichment across payers, “reducing the need for organizations to build and maintain separate payer integrations.” The reach it prints on this release: connections to 95%+ of health plans and 4.5 million-plus providers. The About line adds over 2,000 trading partners.
| What shipped | What Availity says |
|---|---|
| How you connect | REST APIs, sandbox access, and MCP tooling, for applications, automation platforms, and customer-managed AI agents. The Q&A says this is not only a developer portal. Direct API integration is one path. Where available, MCP makes approved tools discoverable to the agent the customer chooses. The front door it names is build.availity.com. |
| Initial workflows | Coverage, benefits, and patient estimates. Claims submission, validation, and status. Remittance and payments. Provider access. Prior authorization. The Q&A on the same page says “Healthcare Interoperability” where the body says “provider access,” and it calls the claims set a claims lifecycle. Availity says these are many of the highest-volume workflows, not all of them. |
| What an agent may call | “Certain supported capabilities may be made available as tools” that authorized customer-managed agents can identify and use, subject to permissions, configuration, agreements, and customer oversight. Availity’s sentence: “An agent is only as smart as what it’s plugged into.” |
| What stays in place | Extend “complements” existing payer portals and EDI. It is another way in, not a notice that the portal login or the claim file goes away. |
| Named for later | Appeals, attachments, provider data management, and “other enhanced transactions.” Availity says it expects to add them. They are not in the initial list. |
“Healthcare systems need the ability to allow great ideas to become real solutions faster, where intelligent technology eliminates administrative burden, and people can spend less time navigating administrative barriers and more time delivering better care,” said Russ Thomas, CEO of Availity. “Availity Extend is designed to make that vision a reality by giving innovators the foundation to safely move faster, think bigger, and create meaningful change across healthcare.”
The Q&A is the operating constraint on that sentence. “Are all payers and workflows available with this release?” Availity’s answer: availability depends on the supported capability, payer participation, approvals, contracts, implementation requirements, and release status. A single integration is the product claim. It is not a statement that every plan answers every call.
On April 28, 2026, also from Jacksonville, Availity unveiled Extend as a way to build automation and AI on the network, coordinating execution with live network data rather than copied data. That release did not mention MCP, REST APIs, a sandbox, or a customer test. It said the network “directly connects more than 4,000 payers and 3.5 million providers,” and that Availity powers “more than half of all U.S. healthcare activity each year.” The differentiator it printed was “Coordinated workflows, not point-to-point APIs.” Sean Barrett, chief product officer, said automation investments could focus on outcomes “without recreating foundational connectivity or governance.” The last line set the calendar: an initial set of content and customers in the first half of 2026, “with broader availability planned later in the year.”
November is that later release, and the access method is what changed. Availity now leads with REST APIs, a sandbox, and MCP. It still says the tasks connect into one workflow and that Extend handles the variation across payers. It did not reprint the April “half of U.S. healthcare activity” line, and it did not print a reconciliation of the headcount. April’s About line said over 17,000 trading partners. November’s About line says over 2,000. Neither release defines the term.
Two other Availity pages, opened the same day as the launch, have not caught the newsroom. The Extend product page still says “Availity Extend (coming Nov 2026)” and prints 3.4 million providers and 50% of U.S. healthcare administrative transactions. developer.availity.com tells existing API customers the old portal stays, calls Extend “our new developer experience,” and prints 900,000-plus active providers. Use 4.5 million-plus and 95%+ of health plans for this announcement. Those are the figures in the launch release. Do not average them with the other pages.
The product page does add a useful distinction the newsroom leaves implicit. It says the APIs behind Extend already run in production across eligibility, authorizations, claims, and payments, that direct API access remains, and that Extend is not required to use those APIs. It also says Extend does not introduce new data rights or permissions. On that page, what is new is the developer experience and the activation layer, not a second network.
MSN Healthcare Solutions is the early adopter Availity names. The before picture is the phone. Staff spent 5 to 11 minutes on hold to check one claim’s status and could check three claims on a call, then started over. Availity says a backlog would have taken days by hand. With Extend, MSN spent a few hours using AI-assisted coding to build the automation. That is software coding, the way Availity describes it, not medical coding. In one test, the automation checked the status of 126 claims in 30 seconds, against at least six hours of manual effort.
Availity then says MSN identified a problem, built its own solution, and put it to work in hours rather than weeks, without a vendor or another technical team. The release does not say how many claims are in the backlog, whether the 126 were a sample or a day’s worklist, or what happened to a claim the status check could not resolve. It does not publish a denial rate, a clean-claim rate, or a dollar.
This is RevCycleAI’s read.
The workflows in the initial list are the ones that still burn a portal login, a status file, or a hold queue. Coverage and the patient estimate. Claim submission and the edit before it goes. Claim status, which in a billing shop is a 276/277-type check, a portal lookup, or the phone call MSN described. Availity did not name an X12 transaction. Remittance and payment. Prior authorization. Appeals are the work this release points to later. If your backlog is attachments and appeal packets, this launch does not say those tools are on.
Availity is not selling you the agent. It says you manage the agent, and that an MCP tool appears only inside the permissions, configuration, agreements, and oversight you already have. The product page says the data rights do not expand. The network wants to be the governed pipe. The agent, and the accountability for what it submits, stay with the customer or with the vendor the customer hired to run it.
If you sell revenue-cycle software and the thing you maintain is the payer connection, this sentence is aimed at you. Extend is supposed to reduce the need to build and keep separate payer integrations. That does not retire the vendor. Payer participation is qualified, appeals are not in the first list, and a long-tail plan that never answers a status API is still your problem. What gets squeezed first is the narrow status bot and the eligibility scrape. What does not get answered here is the exception, the denial strategy, and who is on the hook when the tool returns the wrong benefit.
If you run the billing shop in-house, the MSN story is the pitch at booth 5054. A few hours, then 126 statuses in half a minute. Take the workflow into a staff meeting. Leave the 30 seconds out of the forecast until you run it on your plans, under your permissions. The portal and the EDI file stay. Availity says Extend complements them. Same morning, Greenway said eligibility and prior auth now sit inside the ambulatory platform. Different door. Greenway is the system of record absorbing the step. Availity is the network offering the step to whatever application or agent you point at it. A practice can end up with both, and with a vendor still in the middle. This release does not say which one wins the workflow.
Availity launched Extend on November 16 with REST APIs, a sandbox, and MCP tooling for customer-managed agents, on a network it says reaches 95%+ of health plans and 4.5 million-plus providers. The initial workflows are coverage and estimates, claims submission, validation, and status, remittance, provider access, and prior authorization. The 126 claims in 30 seconds are one MSN test Availity reported. Appeals are not in the initial set, and Availity says each workflow still depends on the payer.
If you are renewing an eligibility or claim-status vendor, ask which of those calls can go through Extend under the permissions you already have, and which plans are actually on for that workflow. If you are building the agent yourself, the release says you keep the agent and the oversight. Availity did not publish a price, a plan-by-workflow list, or a result beyond one test. The product page still said “coming Nov 2026” on the day the newsroom said launched. Read the newsroom for what shipped, and ask which tool your agent can call this week.
What an agent can call, which workflow is still later, and which number is one customer’s test.
Sources: Availity, “Availity Extend Securely Opens the Nation’s Largest Health Intelligence Network to Builders, Automation and AI Agents,” November 16, 2026, Jacksonville, FL (page opened, including the media Q&A). Business Wire, same headline, item 20261116518884 (the portion retrieved matches the newsroom dateline, the REST, sandbox, and MCP sentence, the 95%+ and 4.5 million-plus figures, the initial workflows, and the Russ Thomas quote). Availity, “Introducing Availity Extend for AI & Automation Innovation,” April 28, 2026, Jacksonville, Fla. (page opened; no MCP, REST, sandbox, or MSN test). Business Wire, April 28, 2026, item 20260428607674 (linked as the wire of that introduction; the comparison uses the Availity newsroom page, which was the page opened). availity.com/availity-extend-4 and developer.availity.com (both opened November 16, 2026). The Thomas and Barrett quotes are verbatim from the releases cited. The 126 claims, 30 seconds, six hours, 5–11 minutes, and three-claims-per-call figures are Availity’s account of one MSN test. No production volume is inferred. The 4,000 payers, 3.5 million providers, 17,000 trading partners, 3.4 million providers, 50% of administrative transactions, and 900,000-plus active providers are left on the pages that printed them.