Inbound Health
Inbound Health was a Minneapolis, Minnesota company that enabled health systems and health plans to deliver hospital-level and skilled-nursing-level care in patients' homes. It was spun out of Allina Health's own Hospital-at-Home and SNF-at-Home programs in October 2022 with $20 million from Flare Capital Partners, and was led by co-founder and chief executive Dave Kerwar, previously chief product officer at Mount Sinai Health System, with Dr. Chi Huang as chief medical officer and Dave Zimmerman as chief operating officer. The company raised a $30 million Series B in September 2023 led by HealthQuest Capital, and in February 2024 released Inbound InHome, a proprietary patient-management and analytics platform for advanced care in the home: AI/ML-assisted identification and eligibility screening of candidate patients, device-agnostic biometric monitoring across devices, wearables and in-home sensors, a virtual care module carrying real-time video, audio, text and alerting between patient and care team, a workflow application automating logistics across the care episode, supply-chain management, and integration points into multiple EMRs. Inbound Health ceased operations in December 2025 after regulatory uncertainty over the federal Acute Hospital Care at Home (AHCAH) waiver stalled its next financing round; MedArrive acquired its AI-backed care-navigation technology assets in March 2026. Inbound InHome was sold only under signed health-system and health-plan agreements, and no public developer portal, API reference, SDK, or machine-readable specification (OpenAPI, AsyncAPI, GraphQL SDL, MCP manifest or A2A agent card) was ever published on an Inbound Health host. Both inboundhealth.com and www.inboundhealth.com now fail at the origin behind Cloudflare (HTTP 526) and every api/docs/developer/app/portal/status subdomain has been removed from DNS, so there is no live API surface to catalog. This profile is retained as a historical record.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Inbound Health the way a machine reads it — 1 machine-readable artifact, 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 — Inbound Health scores 2.9/100 (minimal), 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.
Why this profile is thin
Inbound Health ceased operations in December 2025 and MedArrive bought its care-navigation technology assets in March 2026; inboundhealth.com now answers Cloudflare HTTP 526 on every HTTPS path because its origin is gone, plain HTTP returns an identical "Site is not available" 404 page on every path including a nonsense control, none of the api/docs/developer/app/portal/status subdomains resolve in DNS, and the InboundHealth GitHub organization has zero public repositories, so there is no surface left to profile.
This is an honest zero, not a gap in our research. Inbound Health does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://inboundhealth.com/→ HTTP 526https://inboundhealth.com/openapi.json→ HTTP 526https://inboundhealth.com/.well-known/agent-card.json→ HTTP 526https://inboundhealth.com/llms.txt→ HTTP 526http://inboundhealth.com/zzz-does-not-exist-9f3a→ HTTP 404https://api.github.com/users/InboundHealth→ HTTP 200
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
How this is scored →scored 2026-08-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from Inbound Health'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/inbound-health/"
title="Inbound Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/inbound-health.svg"
alt="Inbound Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/inbound-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/inbound-health/"
title="Inbound Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/inbound-health/card.svg"
alt="Inbound Health Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Inbound Health
Each block below is one kind of artifact we hold for Inbound Health. 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 1
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.
Resources
Every other property we hold for Inbound Health — 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.
Access & Security 1
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/inbound-health · machine-readable index on apis.io
This is an independent, third-party profile of Inbound Health, 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.