Zus Health website screenshot

Zus Health

Zus Health is a shared health-data platform that aggregates a patient's clinical history from external networks into the Zus Aggregated Profile (ZAP). It exposes a FHIR R4 (v4.0.1) REST API secured with OAuth2 Bearer tokens, Patient History APIs, document ingestion and retrieval, Zushooks webhooks, a GraphQL FHIR Query Service, and embeddable open-source React components.

Zus Health publishes 5 APIs on the APIs.io network, including Auth API, Documents API, FHIR API, and 2 more. Tagged areas include Health, FHIR, Interoperability, Patient Data, and Healthcare.

The Zus Health catalog on APIs.io includes 1 event-driven AsyncAPI specification.

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

🌐 Visit website 📡 Source on GitHub
54.2/100 developing ▼ -8.5 Agent 34/100 agent ready Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
AccessFreeSelf serve⚡ Free to try
7 APIs 1 MCP Servers
HealthFHIRInteroperabilityPatient DataHealthcare

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 54.2/100 · developing
Contract Quality 6.0 / 21
Developer Ergonomics 7.6 / 17
Access Clarity 11.0 / 17
Operational Transparency 9.0 / 11
Contract Governance 1.9 / 10
Discoverability 6.9 / 9
Regulatory Posture 7.1 / 15
Agent readiness — 34/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 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 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/zus: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 7

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

Zus Health Auth API

OAuth2 token issuance and exchange.

Zus Health Documents API

DocumentReference and Binary resources.

Zus Health FHIR API

General FHIR R4 resources.

Zus Health Patient API

FHIR R4 Patient resources.

Zus Health Patient History API

Jobs that retrieve external data into the Zus Aggregated Profile.

Zus FHIR & Platform API

Zus FHIR R4 REST API plus Auth Service and Patient History APIs. Implements FHIR R4 (v4.0.1) across 128 resource types with instance-level CRUD, transaction Bundles, conditional...

Zus FHIR GraphQL API (FQS)

The Zus FHIR Query Service (FQS) is a read-only GraphQL API over the FHIR data model, exposed at a single endpoint. Supports UPID-scoped (one-human) and builder-scoped queries a...

Scroll for all 7

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Zus Health Auth API

OPEN COLLECTION

Zus Health Auth Documents API

OPEN COLLECTION

Zus Health Auth FHIR API

OPEN COLLECTION

Zus Health Auth Patient API

OPEN COLLECTION

Zus Health Auth Patient History API

OPEN COLLECTION

Zus Health API

OPEN COLLECTION

Scroll for all 7

MCP Servers 1

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

Zus Health MCP Server

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Zus Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Zus Rate Limits

4 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Zus Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Zus Zushooks

ASYNCAPI

Security Posture 2

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

Zus Authentication

http · 1 scheme

SECURITY

Zus Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Zus Agentic Access

15 operations · 7 acting

15 operations · 7 acting

AGENTIC

Resources

Get Started 6

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp
 Login
Login
 Sandbox
Sandbox
 Sandbox
Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation
Documentation
 Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 LLMsTxt
LLMsTxt
 MCPServer
MCPServer
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt
 MCPServer
MCPServer

Design & Contract 16

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 Lifecycle
Lifecycle
 Webhooks
Webhooks
 Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Components
Components
 Conventions
Conventions
 Idempotency
Idempotency
 Lifecycle
Lifecycle
 Webhooks
Webhooks
 Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Components
Components

Scroll for all 16

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Postman
Postman

Access & Security 7

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication
 Compliance
Compliance
 Authentication
Authentication
 DomainSecurity
DomainSecurity
 Authentication
Authentication
 DomainSecurity
DomainSecurity

Scroll for all 7

Operate 7

Status, limits, changes, and where to get help

RateLimits
RateLimits
 Support
Support
 StatusPage
StatusPage
 Deprecation
Deprecation
 ChangeLog
ChangeLog
 Deprecation
Deprecation
 ChangeLog
ChangeLog

Scroll for all 7

Commercial 4

Pricing, plans, and the legal terms of use

Plans
Plans
 FinOps
FinOps
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 4

The organization behind the API

LinkedIn
LinkedIn
 Website
Website
 Blog
Blog
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: zus
url: https://raw.githubusercontent.com/api-evangelist/zus/refs/heads/main/apis.yml
name: Zus Health
kind: company
description: Zus Health is a shared health-data platform that aggregates a patient's clinical history from external networks
  into the Zus Aggregated Profile (ZAP). It exposes a FHIR R4 (v4.0.1) REST API secured with OAuth2 Bearer tokens, Patient
  History APIs, document ingestion and retrieval, Zushooks webhooks, a GraphQL FHIR Query Service, and embeddable open-source
  React components.
accessModel:
  pricing: free
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Free · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zus.png
tags:
- Health
- FHIR
- Interoperability
- Patient Data
- Healthcare
created: '2026-06-21'
modified: '2026-06-21'
specificationVersion: '0.23'
apis:
- aid: zus:zus-auth-api
  name: Zus Health Auth API
  description: OAuth2 token issuance and exchange.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  tags:
  - Authentication
  tags_raw:
  - Auth
  properties:
  - type: OpenAPI
    url: openapi/zus-auth-api-openapi.yml
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-api
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/accessing-the-zap
  - type: Documentation
    url: https://docs.zushealth.com/docs/zap-basics
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Documentation
    url: https://docs.zushealth.com/docs/ingesting-documents
  - type: Documentation
    url: https://docs.zushealth.com/docs/zushooks
- aid: zus:zus-documents-api
  name: Zus Health Documents API
  description: DocumentReference and Binary resources.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  tags:
  - Documents
  properties:
  - type: OpenAPI
    url: openapi/zus-documents-api-openapi.yml
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-api
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/accessing-the-zap
  - type: Documentation
    url: https://docs.zushealth.com/docs/zap-basics
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Documentation
    url: https://docs.zushealth.com/docs/ingesting-documents
  - type: Documentation
    url: https://docs.zushealth.com/docs/zushooks
- aid: zus:zus-fhir-api
  name: Zus Health FHIR API
  description: General FHIR R4 resources.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  tags:
  - FHIR
  properties:
  - type: OpenAPI
    url: openapi/zus-fhir-api-openapi.yml
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-api
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/accessing-the-zap
  - type: Documentation
    url: https://docs.zushealth.com/docs/zap-basics
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Documentation
    url: https://docs.zushealth.com/docs/ingesting-documents
  - type: Documentation
    url: https://docs.zushealth.com/docs/zushooks
- aid: zus:zus-patient-api
  name: Zus Health Patient API
  description: FHIR R4 Patient resources.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  tags:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/zus-patient-api-openapi.yml
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-api
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/accessing-the-zap
  - type: Documentation
    url: https://docs.zushealth.com/docs/zap-basics
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Documentation
    url: https://docs.zushealth.com/docs/ingesting-documents
  - type: Documentation
    url: https://docs.zushealth.com/docs/zushooks
- aid: zus:zus-patient-history-api
  name: Zus Health Patient History API
  description: Jobs that retrieve external data into the Zus Aggregated Profile.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  tags:
  - Patient History
  properties:
  - type: OpenAPI
    url: openapi/zus-patient-history-api-openapi.yml
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-api
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/accessing-the-zap
  - type: Documentation
    url: https://docs.zushealth.com/docs/zap-basics
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Documentation
    url: https://docs.zushealth.com/docs/ingesting-documents
  - type: Documentation
    url: https://docs.zushealth.com/docs/zushooks
- name: Zus FHIR & Platform API
  description: Zus FHIR R4 REST API plus Auth Service and Patient History APIs. Implements FHIR R4 (v4.0.1) across 128 resource
    types with instance-level CRUD, transaction Bundles, conditional create/update/delete by identifier, and version-aware
    writes via the Zus-If-Match ETag header. OAuth 2.0 bearer authentication; machine-to-machine app clients supported.
  humanURL: https://docs.zushealth.com/docs/fhir-api
  baseURL: https://api.zusapi.com/fhir
  properties:
  - type: APIReference
    url: https://docs.zushealth.com/reference/general
  - type: Documentation
    url: https://docs.zushealth.com/docs/fhir-rest-api-capabilities
  - type: Conformance
    url: conformance/zus-fhir-capabilitystatement.json
- name: Zus FHIR GraphQL API (FQS)
  description: The Zus FHIR Query Service (FQS) is a read-only GraphQL API over the FHIR data model, exposed at a single endpoint.
    Supports UPID-scoped (one-human) and builder-scoped queries across resource types in the Designated Record Set. Uses the
    same OAuth 2.0 bearer token as the REST API. Beta.
  humanURL: https://docs.zushealth.com/docs/graphql-api
  baseURL: https://fqs.zusapi.com/query
  properties:
  - type: APIReference
    url: https://fqs-docs.zusapi.com/
  - type: Documentation
    url: https://docs.zushealth.com/docs/graphql-api
common:
- type: AgenticAccess
  url: agentic-access/zus-agentic-access.yml
- type: DomainSecurity
  url: security/zus-domain-security.yml
- type: Authentication
  url: authentication/zus-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/zushealth
- type: Website
  url: https://zushealth.com
- type: Documentation
  url: https://docs.zushealth.com
- type: Plans
  url: plans/zus-plans-pricing.yml
- type: RateLimits
  url: rate-limits/zus-rate-limits.yml
- type: FinOps
  url: finops/zus-finops.yml
- url: https://zushealth.com/feed/
  type: Blog
- type: DeveloperPortal
  url: https://docs.zushealth.com/docs
- type: Documentation
  url: https://docs.zushealth.com/docs/intro-to-zus
- type: APIReference
  url: https://docs.zushealth.com/reference/general
- type: GettingStarted
  url: https://docs.zushealth.com/docs/getting-started-with-the-zap
- type: Support
  url: https://docs.zushealth.com/contact-support
- type: Blog
  url: https://zushealth.com/team/blog/
- type: GitHubOrganization
  url: https://github.com/zushealth
- type: SignUp
  url: https://docs.zushealth.com/page/sign-up
- type: Login
  url: https://app.zushealth.com
- type: TermsOfService
  url: https://zushealth.com/website-terms-of-use/
- type: PrivacyPolicy
  url: https://zushealth.com/website-privacy-policy/
- type: StatusPage
  url: https://status.zusapi.com/
- type: Postman
  url: https://www.postman.com/zus-health/workspace/zus-health-workspace
- type: Compliance
  url: https://zushealth.com/platform/
- type: LLMsTxt
  url: llms/zus-llms.txt
- type: Authentication
  url: authentication/zus-authentication.yml
- type: Conventions
  url: conventions/zus-conventions.yml
- type: Idempotency
  url: conventions/zus-conventions.yml
- type: Lifecycle
  url: lifecycle/zus-lifecycle.yml
- type: Deprecation
  url: lifecycle/zus-lifecycle.yml
- type: ChangeLog
  url: changelog/zus-changelog.yml
- type: Webhooks
  url: asyncapi/zus-zushooks.yml
- type: Conformance
  url: conformance/zus-conformance.yml
- type: ErrorCatalog
  url: errors/zus-problem-types.yml
- type: DomainSecurity
  url: security/zus-domain-security.yml
- type: MCPServer
  url: mcp/zus-mcp.yml
- type: DataModel
  url: data-model/zus-data-model.yml
- type: Sandbox
  url: sandbox/zus-sandbox.yml
- type: Components
  url: components/zus-components.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/zus-llms.txt
- type: Authentication
  url: authentication/zus-authentication.yml
- type: Conventions
  url: conventions/zus-conventions.yml
- type: Idempotency
  url: conventions/zus-conventions.yml
- type: Lifecycle
  url: lifecycle/zus-lifecycle.yml
- type: Deprecation
  url: lifecycle/zus-lifecycle.yml
- type: ChangeLog
  url: changelog/zus-changelog.yml
- type: Webhooks
  url: asyncapi/zus-zushooks.yml
- type: Conformance
  url: conformance/zus-conformance.yml
- type: ErrorCatalog
  url: errors/zus-problem-types.yml
- type: DomainSecurity
  url: security/zus-domain-security.yml
- type: MCPServer
  url: mcp/zus-mcp.yml
- type: DataModel
  url: data-model/zus-data-model.yml
- type: Sandbox
  url: sandbox/zus-sandbox.yml
- type: Components
  url: components/zus-components.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/zus"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/zus/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/zus/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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