How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Healthy.io

Healthy.io is a digital-health company that turns an ordinary smartphone camera into a clinical-grade measurement device, using colorimetric analysis, computer vision and machine learning trained on more than a million tagged color-spectrum images. Its Minuteful product line covers home urinalysis for chronic kidney disease (Minuteful Kidney, FDA 510(k) cleared and CE marked), urinary tract infection testing (Minuteful UTI), a ten-parameter urinalysis panel (Minuteful 10), and digitized chronic wound assessment (Minuteful for Wound). The company sells to health systems, provider groups and payers - including Medicare Advantage and nonprofit health plans - rather than to developers, and states that its technology integrates into most EMRs via SMART on FHIR. Healthy.io operates from Boston, London and Tel Aviv, and publishes a detailed public trust center covering security, privacy, availability and compliance, including a coordinated vulnerability disclosure policy.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Healthy.io the way a machine reads it — 4 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 — Healthy.io scores 21.9/100 (emerging), 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.

Behind a wall

Why this profile is thin

Healthy.io runs a documentation host and a status host, but both docs.healthy.io and status.healthy.io 302-redirect every path to a healthyio.cloudflareaccess.com SSO login, so the EMR/SMART-on-FHIR integration surface the homepage advertises cannot be read, parsed or evaluated by anyone without a Healthy.io identity.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Healthy.io's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

What we probed
  • https://docs.healthy.io/HTTP 302
  • https://status.healthy.io/HTTP 302
  • https://healthy.io/.well-known/smart-configurationHTTP 404
  • https://healthy.io/developersHTTP 404

Checked 2026-08-22. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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-08-24 · rubric v0.12.1
Composite quality — 21.9/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.0 / 20
Access Clarity 7.4 / 20
Operational Transparency 1.7 / 13
Contract Governance 2.2 / 12
Discoverability 5.7 / 10
Regulatory · Health 6.8 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Healthy.io Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Healthy.io's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/healthy.io/"
   title="Healthy.io on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/healthy.io.svg"
       alt="Healthy.io Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Healthy.io

Each block below is one kind of artifact we hold for Healthy.io. 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.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Security Posture 3

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.

Healthy.Io Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Healthy.Io Vulnerability Disclosure

Hackerone · contact published

SECURITY

Healthy.Io Trust Center

ISO/IEC 27001:2013, ISO 22301:2019, ISO 13485:2016, HITRUST, UK Cyber Essentials, NHS Data Security and Protection Toolkit

SECURITY

Resources

Every other property we hold for Healthy.io — 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.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

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

Where this information came from

This is an independent, third-party profile of Healthy.io, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.