HealthEx

HealthEx is a patient-centric health-data-rights platform that securely unifies an individual's medical records across places of care into one connected history, and lets them share that record — under explicit, patient-initiated consent — with providers, apps, and AI services. It operates as an Information Access Services (IAS) Provider on the TEFCA network, complies with HIPAA privacy rules, and reaches records across more than 80% of U.S. care providers. For developers HealthEx exposes a REST admin API (patient outreach, consent checking and auditing, record-location search, usage), a FHIR R4 server ($everything, USCDIv3), and a hosted Model Context Protocol server that gives AI agents governed, consent-scoped access to a patient's health record.

HealthEx is listed with 1 API on the APIs.io network. Tagged areas include Company, Healthcare, Health Records, FHIR, and Patient Consent.

HealthEx’s developer surface includes engineering blog, documentation, API reference, getting-started guide, support, signup flow, authentication, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

37.2/100 thin ▬ flat Agent 31/100 agent ready Front door AI 6/6 dominant Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers 3 Agent Skills

Company Healthcare Health Records FHIR Patient Consent Data Sharing Interoperability TEFCA MCP Agents

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 37.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 4.9 / 17

Operational Transparency 3.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 6.2 / 15

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/healthex/"><img src="https://apis.io/badge/healthex/card.svg" alt="HealthEx on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 28.9 — up to +14.2 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/healthex/apis.yml: open an issue on github.com/api-evangelist/healthex to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Certified Health IT (health IT accreditation and certification registers)	standard	53.3	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

HealthEx API

REST API for patient outreach, consent checking and auditing, record-location search, test-patient creation, and usage reporting, plus a FHIR R4 server ($everything) for standar...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

HealthEx MCP Server

Hosted Model Context Protocol server exposing a consented patient's FHIR-based health record to AI agents through standardized tools, with per-patient data isolation and natural...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Add patients to a study and track record retrieval

AGENT SKILL

Check consent then fetch the full FHIR record

AGENT SKILL

Retrieve a patient's health summary via MCP

AGENT SKILL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Healthex Authentication

http/oauth2 · 2 schemes

SECURITY

Healthex Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Healthex Trust Center

HIPAA, TEFCA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Healthex Scopes

5 scopes · authorizationCode

5 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

TrustCenter

Compliance

Authentication

OAuthScopes

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

StatusPage

Deprecation

ChangeLog

Company 2

The organization behind the API

Blog

Blog

Website

Website

Source (apis.yml)

aid: healthex
name: HealthEx
description: HealthEx is a patient-centric health-data-rights platform that securely unifies an individual's medical records
  across places of care into one connected history, and lets them share that record — under explicit, patient-initiated consent
  — with providers, apps, and AI services. It operates as an Information Access Services (IAS) Provider on the TEFCA network,
  complies with HIPAA privacy rules, and reaches records across more than 80% of U.S. care providers. For developers HealthEx
  exposes a REST admin API (patient outreach, consent checking and auditing, record-location search, usage), a FHIR R4 server
  ($everything, USCDIv3), and a hosted Model Context Protocol server that gives AI agents governed, consent-scoped access
  to a patient's health record.
url: https://raw.githubusercontent.com/api-evangelist/healthex/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://framerusercontent.com/assets/91Fl8WPMZvfgNsG45g8tmHf88w.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: aws-cloudfront
tags:
- Company
- Healthcare
- Health Records
- FHIR
- Patient Consent
- Data Sharing
- Interoperability
- TEFCA
- MCP
- Agents
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: HealthEx API
  description: REST API for patient outreach, consent checking and auditing, record-location search, test-patient creation,
    and usage reporting, plus a FHIR R4 server ($everything) for standards-based access to a consented patient's medical record.
  humanURL: https://docs.healthex.io/
  baseURL: https://api.healthex.io
  properties:
  - type: Documentation
    url: https://docs.healthex.io/
  - type: APIReference
    url: https://docs.healthex.io/api
  - type: GettingStarted
    url: https://docs.healthex.io/authentication
  - type: Authentication
    url: authentication/healthex-authentication.yml
  - type: OAuthScopes
    url: scopes/healthex-scopes.yml
  - type: Sandbox
    url: sandbox/healthex-sandbox.yml
  - type: ChangeLog
    url: changelog/healthex-changelog.yml
  - type: MCPServer
    url: mcp/healthex-mcp.yml
common:
- url: https://www.healthex.io/press
  type: Blog
- type: DomainSecurity
  url: security/healthex-domain-security.yml
- type: Website
  url: https://www.healthex.io/
- type: DeveloperPortal
  url: https://docs.healthex.io/
- type: Documentation
  url: https://docs.healthex.io/
- type: APIReference
  url: https://docs.healthex.io/api
- type: GettingStarted
  url: https://docs.healthex.io/authentication
- type: Support
  url: https://support.healthex.io/kb
- type: SignUp
  url: https://app.healthex.io/
- type: Login
  url: https://app.healthex.io/
- type: StatusPage
  url: https://status.healthex.io/
- type: TrustCenter
  url: https://trustcenter.healthex.io/
- type: Compliance
  url: https://trustcenter.healthex.io/
- type: Authentication
  url: authentication/healthex-authentication.yml
- type: OAuthScopes
  url: scopes/healthex-scopes.yml
- type: WellKnown
  url: well-known/healthex-well-known.yml
- type: MCPServer
  url: mcp/healthex-mcp.yml
- type: LLMsTxt
  url: llms/healthex-llms.txt
- type: Conventions
  url: conventions/healthex-conventions.yml
- type: ErrorCatalog
  url: errors/healthex-problem-types.yml
- type: Lifecycle
  url: lifecycle/healthex-lifecycle.yml
- type: StatusPage
  url: lifecycle/healthex-lifecycle.yml
- type: Deprecation
  url: lifecycle/healthex-lifecycle.yml
- type: ChangeLog
  url: changelog/healthex-changelog.yml
- type: Sandbox
  url: sandbox/healthex-sandbox.yml
- type: Conformance
  url: conformance/healthex-conformance.yml
- type: DataModel
  url: data-model/healthex-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

HealthEx API — frequently asked questions

Does HealthEx have an API?

Yes. APIs.io lists 1 API from HealthEx, including HealthEx API.

How do I authenticate with the HealthEx API?

HealthEx documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Healthex Authentication.

Does HealthEx have an MCP server?

Yes. APIs.io lists 1 MCP server for HealthEx: Hosted Model Context Protocol server exposing a consented patient's FHIR-based health record to AI agents through standardized tools, with per-patient data isolation and natural-language search. Also

Is the HealthEx API ready for AI agents?

HealthEx has a Kin Score of 37.2 out of 100 (thin) and an Agent Readiness score of 31.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/healthex"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/healthex/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/healthex/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.