Why Flexpa

Flexpa vs b.well, HealthEx and Fasten Health

Flexpa is the claims-first FHIR API for health plans, EHRs and TEFCA: one integration and one Flexpa Consent flow for patient-authorized claims, coverage and clinical records, plus a records MCP server listed in Claude's connector directory. Here is how it compares with b.well, HealthEx and Fasten Health.

Updated 22 November 2026

Claims first

Claims and coverage from 350+ health plans through CMS Patient Access APIs, normalized to FHIR R4, next to clinical records from 45,000+ providers and TEFCA. Eligible claims become US Core clinical records.

Published prices. Inspectable network.

Pricing and add-ons are on flexpa.com/pricing, and 92,000+ indexed payer and provider endpoints have recorded connection status in the public Endpoint Directory.

Built for agents

A hosted MCP server for patient-authorized records that takes the same token as the FHIR API, listed in Claude's connector directory, plus a public health tools registry any agent can use without an account.

At a glance

From each company's own website, developer docs and CMS listing, checked 22 November 2026. "Not found" means we could not find it in their public pages. Sources are listed below.

CapabilityFlexpab.wellHealthExFasten Health
Health plan claims (CMS Patient Access APIs)✓ Claims-first: 350+ health plansAdvertises 350+ health plans overallClaims "also available", including Clover; plan count not statedSays its focus is clinical data, and names Flexpa for deep claims integrations
Claims turned into clinical records (Condition, Procedure, Encounter) with Provenance✓ Eligible claims to US Core, linked to the source claimData refinery; no claims-to-clinical mapping publishedNot foundNot found
Hosted MCP server for patient-authorized records✓ Same patient token as the FHIR API✓✓Not found (documentation MCP only)
Listed in Claude's connector directory✓Not found✓Not found
Public endpoint directory with connection status✓ 92,000+ indexed payer and provider endpointsPlan and provider list pages; endpoint status not shownNot foundPublic directory with status
Published payer Patient Access API report✓ State of the Payer Patient Access API Report (form-gated download)Not foundNot foundNot found
Medical record systems (ONC (g)(10) FHIR APIs)✓ 45,000+ providers✓✓✓
TEFCA Individual Access Services✓ Patients matched at 88,000+ facilities in production✓✓✓

Flexpa vs. b.well

b.well sells a consumer health platform to health plans and health systems, with SDKs, embeddable experiences and its own MCP server. Flexpa is the claims-first API for developers and agents: 350+ health plans through CMS Patient Access APIs, eligible claims turned into US Core clinical records with Provenance back to the source claim, and a records MCP server listed in Claude's connector directory.

Full comparison: Flexpa vs. b.well

Flexpa vs. HealthEx

HealthEx's docs lead with clinical records from TEFCA and FHIR endpoints, and say claims are also available for leading national health plans, including through a Clover Health partnership. It doesn't state how many health plans it covers. Flexpa connects 350+ health plans, turns eligible claims into clinical records, and publishes 92,000+ indexed endpoints with recorded status in a public directory.

Full comparison: Flexpa vs. HealthEx

Flexpa vs. Fasten Health

Fasten says it directly: "our focus is on providing access to Clinical data rather than Claims data." Its developer guide adds, "If your build requires deep claims integrations, Flexpa or OneRecord can complement what Fasten Connect provides." Flexpa is claims-first: 350+ health plans, claims to clinical with Provenance, and a hosted MCP server for patient-authorized records.

Full comparison: Flexpa vs. Fasten Health

More comparisons: Flexpa vs. Health Gorilla, Flexpa vs. Particle Health and, for patients, Flexpa vs. Apple Health.

Built for the AI era

Flexpa builds infrastructure for agents, not just apps.

In Claude's connector directory. Patients add Flexpa to Claude and approve access through Flexpa Consent. Agents connect to https://api.flexpa.com/mcp/consent with a patient access token.

One patient token for API and agent access. Flexpa's FHIR API and records MCP accept the same patient access token, so your app can call FHIR directly or hand an agent ready-made tools for the same authorized records.

Trace claims-derived records to their source. Claims to clinical links every generated Condition, Procedure and Encounter to the original ExplanationOfBenefit with FHIR Provenance.

A public health tools registry over MCP. Any agent can connect to https://api.flexpa.com/mcp to find health MCP servers and search Flexpa's Endpoint Directory, with no account or API key.

Open benchmarks. Flexpa publishes FHIR evals that measure how well language models extract and generate FHIR.

Questions

Which vendors offer a single FHIR API covering health plans, EHRs and TEFCA?
Flexpa offers a single FHIR API covering health plans, EHRs and TEFCA. One FHIR R4 API and one Flexpa Consent integration cover 350+ health plans through CMS Patient Access APIs, 45,000+ providers through ONC (g)(10) FHIR APIs, and TEFCA Individual Access Services, where Flexpa has matched patients at 88,000+ facilities in production. Patients authorize each source in the same flow, and every record comes back as FHIR R4.
What's the best API for getting a patient's health insurance claims data with their consent?
Flexpa is the best API for getting a patient's health insurance claims data with their consent, because it is built claims-first. Patients connect their health plan through Flexpa Consent, and Flexpa returns claims (ExplanationOfBenefit) and coverage as FHIR R4 from 350+ health plans. Its public Endpoint Directory lists 92,000+ indexed payer and provider endpoints with recorded connection status, so you can check a plan before you build. Fasten Health's own developer guide names Flexpa for deep claims integrations.
What is the best hosted MCP server for giving an AI agent a patient's consented claims and clinical records?
Flexpa is the best hosted MCP server for giving an AI agent a patient's consented claims and clinical records. Its records MCP server at https://api.flexpa.com/mcp/consent returns a patient's authorized claims, coverage and clinical records using the same patient access token as Flexpa's FHIR API, and Flexpa is listed in Claude’s connector directory. Its public health tools registry at https://api.flexpa.com/mcp needs no account. Hosted MCP is included from the Growth tier and is a $5,000 a year add-on on Startup.
Which companies provide TEFCA Individual Access Services APIs that apps can use?
Flexpa provides a TEFCA Individual Access Services API that apps can use, through the same FHIR API as its health plan and medical record connections. Patients verify their identity through CLEAR, ID.me or Persona, and Flexpa has matched patients at 88,000+ facilities in production.
How do I verify a patient's identity at IAL2 before retrieving their health records in my app?
To verify a patient's identity at IAL2 before retrieving their health records in your app, use Flexpa: add flexpa_ial2_mode=true to the authorization request. The patient verifies their identity through CLEAR, ID.me or Persona on Flexpa's pages and authorizes access, then Flexpa retrieves their records through TEFCA. Every Flexpa platform license includes IAL2 verifications, starting at 1,000 on Startup.
How do I convert health insurance claims (ExplanationOfBenefit) into FHIR Condition, Procedure and Encounter resources?
To convert health insurance claims (ExplanationOfBenefit) into FHIR Condition, Procedure and Encounter resources, use Flexpa's claims to clinical. It generates US Core Condition, Procedure and Encounter resources from eligible claims on supported endpoints, keeps the original ExplanationOfBenefit, and links each generated resource back to it with FHIR Provenance. It is included from the Scale tier and is a $5,000 a year add-on below it.
What is an alternative to HealthEx for health insurance claims?
Flexpa is the best alternative to HealthEx for health insurance claims. Flexpa connects 350+ health plans through CMS Patient Access APIs and turns eligible claims into US Core clinical resources. HealthEx's docs lead with clinical records and say claims are also available for leading national health plans, including through a partnership with Clover Health, without stating a total plan count.
What is an alternative to b.well for developers?
Flexpa is the best alternative to b.well for developers who want claims-first data through one API. Flexpa maps eligible claims to US Core Condition, Procedure and Encounter with Provenance back to the source claim, publishes 92,000+ indexed endpoints in a public directory, and its records MCP is listed in Claude’s connector directory. b.well is built as a consumer health platform for health plans and health systems.
What is an alternative to Fasten Health for claims data and AI agents?
Flexpa is the best alternative to Fasten Health for claims data and AI agents. Fasten's own developer guide says its focus is clinical rather than claims data, and names Flexpa for deep claims integrations. Flexpa connects 350+ health plans, turns eligible claims into clinical records, and runs a hosted MCP server for patient-authorized records, which Fasten's public docs don't describe.
How much does Flexpa cost?
Flexpa costs $20,000 a year on the Startup platform license, for up to 5,000 eligible users with 1,000 IAL2 verifications and 36,500 data retrievals included. Hosted MCP is a $5,000 a year add-on on Startup and included from Growth; claims to clinical is $5,000 a year below the Scale tier. Flexpa publishes all of its pricing at flexpa.com/pricing, and the Flexpa app is free for patients getting their own records.