DispatchHealth

DispatchHealth is a Denver, Colorado-based provider of complex medical care in the home, founded in 2013 and merged with Medically Home in June 2025 to create one of the largest hospital-at-home platforms in the United States. The combined company delivers same-day urgent care, hospital-alternative (hospital-at-home) care, transitional and recovery care across roughly 50 metropolitan areas in partnership with nearly 40 health systems and national payers. Its CESIA technology platform handles rules-based and AI-assisted care planning, dispatching, routing, scheduling, care-team status, real-time two-way patient communications and field equipment tracking, and is designed to integrate with a partner health system's existing EMR rather than replace it. DispatchHealth partners access the platform through the Dispatch Express portal and patients through an online request flow; the company publishes no public developer portal, API documentation, or machine-readable API contract as of this profiling pass.

DispatchHealth is listed with 1 API on the APIs.io network. Tagged areas include Company, Healthcare, Health Systems, Hospital at Home, and Home Care.

DispatchHealth’s developer surface includes authentication, engineering blog, support, FAQ, pricing, signup flow, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.5/100 thin ▬ flat Agent 21/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

1 API 1 MCP Servers

Company Healthcare Health Systems Hospital at Home Home Care Urgent Care Care Delivery Medical Services Telehealth Digital Health

Kin Score

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

Composite quality — 27.5/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 8.7 / 17

Operational Transparency 0.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 4.8 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 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

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/.

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/dispatchhealth/"><img src="https://apis.io/badge/dispatchhealth/card.svg" alt="DispatchHealth 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Developer Ergonomics scores 19.0 — up to +16.2 composite points Ask about this →
Operational Transparency scores 4.8 — up to +12.4 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/dispatchhealth/apis.yml: open an issue on github.com/api-evangelist/dispatchhealth 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 3

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 1

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

DispatchHealth MCP Server

An OAuth 2.1-protected Model Context Protocol (MCP) server exposed on DispatchHealth's own host by the WordPress MCP adapter running on www.dispatchhealth.com. Discovery is full...

MCP Servers 1

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

DispatchHealth MCP Server

Remote MCP server at www.dispatchhealth.com.

MCP SERVER

Terms of Service 1

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

DispatchHealth

7 quoted statements, read from DispatchHealth's own page on 2026-11-09.

TERMS

Privacy & Data 1

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

DispatchHealth

17 quoted statements, read from DispatchHealth's own page on 2026-11-09.

PRIVACY

Eligibility 1

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

DispatchHealth

4 quoted statements, read from DispatchHealth's own page on 2026-11-09.

ELIGIBILITY

Data License 1

How its data and outputs may be reused, quoted from its own terms.

DispatchHealth

1 quoted statement, read from DispatchHealth's own page on 2026-11-09.

LICENSE

Security Posture 3

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

DispatchHealth Authentication

oauth2/http · 2 schemes

SECURITY

DispatchHealth Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

DispatchHealth Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

DispatchHealth Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp

SignUp

Login

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

TrustCenter

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

FAQ

FAQ

Commercial 5

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 6

The organization behind the API

Website

About

Blog

Press

Partners

Careers

Other 5

Properties that don't map to a standard resource type

SecondaryMarket

Technology

Locations

DataProcessing

Eligibility

Source (apis.yml)

aid: dispatchhealth
name: DispatchHealth
description: DispatchHealth is a Denver, Colorado-based provider of complex medical care in the home, founded in 2013 and
  merged with Medically Home in June 2025 to create one of the largest hospital-at-home platforms in the United States. The
  combined company delivers same-day urgent care, hospital-alternative (hospital-at-home) care, transitional and recovery
  care across roughly 50 metropolitan areas in partnership with nearly 40 health systems and national payers. Its CESIA technology
  platform handles rules-based and AI-assisted care planning, dispatching, routing, scheduling, care-team status, real-time
  two-way patient communications and field equipment tracking, and is designed to integrate with a partner health system's
  existing EMR rather than replace it. DispatchHealth partners access the platform through the Dispatch Express portal and
  patients through an online request flow; the company publishes no public developer portal, API documentation, or machine-readable
  API contract as of this profiling pass.
url: https://raw.githubusercontent.com/api-evangelist/dispatchhealth/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
image: https://www.dispatchhealth.com/wp-content/uploads/2025/07/dispatchhealth-logo.svg
specificationVersion: '0.23'
created: '2026-07-31'
modified: '2026-07-31'
x-enrichment:
  date: '2026-07-31'
  status: enriched
  artifacts_added: 11
  pass: local-v1
tags:
- Company
- Healthcare
- Health Systems
- Hospital at Home
- Home Care
- Urgent Care
- Care Delivery
- Medical Services
- Telehealth
- Digital Health
tags_raw:
- Company
- Healthcare
- Health Systems
- Hospital at Home
- Home Health
- Urgent Care
- Care Delivery
- Medical Services
- Telehealth
- Digital Health
apis:
- name: DispatchHealth MCP Server
  description: 'An OAuth 2.1-protected Model Context Protocol (MCP) server exposed on DispatchHealth''s own host by the WordPress
    MCP adapter running on www.dispatchhealth.com. Discovery is fully machine-readable: RFC 8414 authorization-server metadata
    and RFC 9728 protected-resource metadata are both served anonymously, the endpoint returns a conformant WWW-Authenticate
    Bearer challenge, and a single coarse `mcp` scope is advertised. The tool list is auth-gated — an anonymous tools/list
    returns 401 — so no tool manifest is asserted. This surface fronts the marketing site''s content and WordPress abilities;
    DispatchHealth''s clinical/partner platform (CESIA, Dispatch Express) publishes no public API.'
  humanURL: https://www.dispatchhealth.com/
  baseURL: https://www.dispatchhealth.com/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  - OAuth
  - Healthcare
  - Authentication
  tags_raw:
  - MCP
  - Agents
  - OAuth
  - Healthcare
  - Authentication
  properties:
  - type: MCPServer
    url: mcp/dispatchhealth-mcp.yml
  - type: Authentication
    url: authentication/dispatchhealth-authentication.yml
  - type: OAuthScopes
    url: scopes/dispatchhealth-scopes.yml
  - type: WellKnown
    url: well-known/dispatchhealth-well-known.yml
  x-surface: platform-generated
  x-platform: wordpress
  x-platform-surface: mcp-plugin
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/dispatchhealth-domain-security.yml
- type: MCPServer
  url: mcp/dispatchhealth-mcp.yml
- type: WellKnown
  url: well-known/dispatchhealth-well-known.yml
- type: Authentication
  url: authentication/dispatchhealth-authentication.yml
- type: OAuthScopes
  url: scopes/dispatchhealth-scopes.yml
- type: Conformance
  url: conformance/dispatchhealth-conformance.yml
- type: TrustCenter
  url: security/dispatchhealth-trust-center.yml
- type: Compliance
  url: https://trust.dispatchhealth.com/
- type: LLMsTxt
  url: llms/dispatchhealth-llms.txt
- type: Website
  url: https://www.dispatchhealth.com/
- type: SecondaryMarket
  url: https://forgeglobal.com/dispatchhealth_stock/
- type: About
  url: https://www.dispatchhealth.com/about-us/
- type: Blog
  url: https://www.dispatchhealth.com/blog/
- type: Press
  url: https://www.dispatchhealth.com/press-room/
- type: Support
  url: https://www.dispatchhealth.com/get-in-touch/
- type: FAQ
  url: https://www.dispatchhealth.com/faq/
- type: Pricing
  url: https://www.dispatchhealth.com/cost-insurance-coverage/
- type: SignUp
  url: https://request.dispatchhealth.com/
- type: Login
  url: https://express.dispatchhealth.com/
- type: TermsOfService
  url: https://www.dispatchhealth.com/terms-of-service/
- type: PrivacyPolicy
  url: https://www.dispatchhealth.com/privacy-policy/
- type: GitHubOrganization
  url: https://github.com/DispatchHealth
- type: Partners
  url: https://www.dispatchhealth.com/partners/
- type: Technology
  url: https://www.dispatchhealth.com/technology/
- type: Careers
  url: https://www.dispatchhealth.com/careers/
- type: Locations
  url: https://www.dispatchhealth.com/locations/
- type: UsageTerms
  url: terms/dispatchhealth-terms-of-service.yml
- type: DataProcessing
  url: privacy/dispatchhealth-privacy-policy.yml
- type: Eligibility
  url: eligibility/dispatchhealth-eligibility.yml
- type: DataLicense
  url: data-license/dispatchhealth-data-license.yml

DispatchHealth API — frequently asked questions

Does DispatchHealth have an API?

Yes. APIs.io lists 1 API from DispatchHealth, including DispatchHealth MCP Server.

How do I authenticate with the DispatchHealth API?

DispatchHealth documents its authentication (oauth2/http · 2 schemes). The details are profiled on APIs.io as DispatchHealth Authentication.

Does DispatchHealth have an MCP server?

Yes. APIs.io lists 1 MCP server for DispatchHealth: Remote MCP server at www.dispatchhealth.com.

Is the DispatchHealth API ready for AI agents?

DispatchHealth has a Kin Score of 27.5 out of 100 (thin) and an Agent Readiness score of 20.9 (agent-aware), 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/dispatchhealth"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/dispatchhealth/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/dispatchhealth/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.