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 7 API contracts indexed on the APIs.io network, including Auth API, Documents API, FHIR API, and 4 more. Tagged areas include Health, FHIR, Interoperability, Patient Data, and Healthcare.

The Zus Health catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

57.2/100 strong ▬ flat Agent 31/100 agent ready Front door AI 1/6 silent Heartbeat 5/100 dormant saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 1 Agent Skills

Health FHIR Interoperability Patient Data Healthcare

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 57.2/100 · strong

Contract Quality 10.7 / 19

Developer Ergonomics 9.6 / 15

Access Clarity 8.0 / 15

Operational Transparency 5.3 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 31/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 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/zus/"><img src="https://apis.io/badge/zus/card.svg" alt="Zus Health 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified) Ask about this →

4 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 57.3 — up to +10.7 composite points Ask about this →
Access Clarity scores 53.2 — up to +9.4 composite points Ask about this →
Contract Governance scores 31.8 — up to +8.2 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/zus/apis.yml: open an issue on github.com/api-evangelist/zus 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 →

Standards implemented 2

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

OpenAPI

measured — observed by APIs.io (published)

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 6

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

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

Agent Skills 1

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

Authenticate a backend service to the Zus API

AGENT SKILL

Zus Health API pricing

Not yet checked against Zus Health's own pricing page. Compiled by API Evangelist on 2026-06-21 from zushealth.com; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Sandbox free	—
Platform Partnership enterprise	—

Plan details, limits and sources →

Rate limits

Token Endpoint Requests: 200 per hour requests
FHIR Search Page Size: 10 default, 500 maximum resources
Bundle Entries: 100 entries

Compiled by API Evangelist, not yet checked against Zus Health's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Zus Health Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Zus Health Rate Limits

4 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Zus Health

9 quoted statements, read from Zus Health's own page on 2026-11-10.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Zus Health

13 quoted statements, read from Zus Health's own page on 2026-11-10.

PRIVACY

Compliance 1

Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.

Zus Health

3 quoted statements, read from Zus Health's own page on 2026-11-10.

COMPLIANCE

Eligibility 1

Who may sign up and where, quoted from its own terms.

Zus Health

4 quoted statements, read from Zus Health's own page on 2026-11-10.

ELIGIBILITY

FinOps 1

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

Zus Health Finops

FINOPS

Event Specifications 1

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

Zus Zushooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Zus Health API Rules

59 rules · 57 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

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

Zus Health Authentication

http · 1 scheme

SECURITY

Zus Health Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

Zus Health Agentic Access

15 operations · 7 acting

AGENTIC

Resources

Get Started 6

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

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

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 16

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Lifecycle

Webhooks

Conformance

ErrorCatalog

DataModel

Components

Conventions

Idempotency

Lifecycle

Webhooks

Conformance

ErrorCatalog

DataModel

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

Authentication

Compliance

Authentication

DomainSecurity

Authentication

DomainSecurity

Scroll for all 7

Operate 7

Status, limits, changes, and where to get help

RateLimits

Support

StatusPage

Deprecation

ChangeLog

Deprecation

ChangeLog

Scroll for all 7

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

TermsOfService

PrivacyPolicy

UsageTerms

Company 4

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Blog

Blog

Other 3

Properties that don't map to a standard resource type

DataProcessing

DataProcessing

Attestations

Attestations

Eligibility

Eligibility

Source (apis.yml)

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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zus.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
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:
  - Patients
  tags_raw:
  - 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: X-MCPServerCandidate
  url: mcp/zus-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- 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: X-MCPServerCandidate
  url: mcp/zus-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DataModel
  url: data-model/zus-data-model.yml
- type: Sandbox
  url: sandbox/zus-sandbox.yml
- type: Components
  url: components/zus-components.yml
- type: UsageTerms
  url: terms/zus-terms-of-service.yml
- type: DataProcessing
  url: privacy/zus-privacy-policy.yml
- type: Attestations
  url: compliance/zus-compliance.yml
- type: Eligibility
  url: eligibility/zus-eligibility.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Zus Health API — frequently asked questions

Does Zus Health have an API?

Yes. APIs.io lists 7 APIs from Zus Health, including Zus Health Auth API, Zus Health Documents API and Zus Health FHIR API, and 4 more.

Is there an OpenAPI specification for the Zus Health API?

Yes. APIs.io indexes 5 OpenAPI specifications for Zus Health, each linked for download from this page.

How do I authenticate with the Zus Health API?

Zus Health uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Zus Health Authentication.

How much does the Zus Health API cost?

APIs.io lists 2 pricing plans for Zus Health, with each plan's price, limits and inclusions under Pricing on this page.

Is the Zus Health API ready for AI agents?

Zus Health has a Kin Score of 57.2 out of 100 (strong) and an Agent Readiness score of 31.1 (agent-ready), scored by API Evangelist on 2026-11-13.

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"

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.