Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Health Universe website screenshot

Health Universe

Health Universe is an enterprise healthcare AI platform and compliant app cloud that lets clinical, research, and life-sciences teams build, deploy, govern, and monitor AI agents inside regulated environments. Developers package Python models as Streamlit, FastAPI, React, or Agent2Agent (A2A) apps and ship them with one click to a HIPAA-aligned, SOC 2 Type II, ONC-certified, TEFCA-connected workspace. The platform unifies patient records via TEFCA and SMART on FHIR, and provides Navigator, Explorer/Roster, and Observer surfaces for deploying agents, building cohorts, and monitoring cost, hallucination, and high-risk scenarios with human-in-the-loop review. Health Universe ships a first-party CLI (@health-universe/cli), a Python SDK, and an A2A agent SDK. Backed by Kleiner Perkins.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Health Universe the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Health Universe scores 33.0/100 (thin), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 33.0/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 10.9 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Health 7.8 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Health Universe

Each block below is one kind of artifact we hold for Health Universe. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Health Universe Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Health Universe Trust Center

SOC 2, HIPAA

SECURITY

Resources

Every other property we hold for Health Universe — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/health-universe · machine-readable index on apis.io