Eko Health

Eko Health Inc. is an Oakland, California digital health company that builds FDA-cleared digital stethoscopes (CORE 500, CORE Digital Attachment, DUO, and the 3M Littmann CORE) together with cloud software and AI algorithms for the detection of cardiovascular and pulmonary disease. Its platform pairs the hardware with the Eko App (iOS/Android), the Eko web Dashboard, Eko AI murmur/AFib/low-ejection-fraction detection, and SENSORA, an enterprise AI cardiac disease detection platform for health systems. For integrators Eko publishes Eko Connect — an Enterprise SDK and API surface that live-streams auscultation audio and single-lead ECG into third-party telehealth, telemedicine cart, and life-science applications. The Enterprise SDK and its backing REST API at api.ekodevices.com are commercially gated: there is no public developer portal, OpenAPI, or self-serve documentation, and access is arranged through Eko sales. The company's public agent-facing surface is its Shopify storefront, which serves a live anonymous MCP server, an agents.md / llms.txt, and Universal Commerce Protocol discovery.

Eko Health is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Health, Healthcare, Medical Devices, and Digital Health.

Eko Health’s developer surface includes engineering blog, support, pricing, signup flow, authentication, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.5/100 thin ▬ flat Agent 18/100 agent aware Front door AI 5/6 prominent saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessFreemiumSelf serve⚡ Free to try

2 APIs 1 MCP Servers

Company Health Healthcare Medical Devices Digital Health Telehealth Artificial Intelligence Cardiology Remote Patient Monitoring Commerce

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 38.5/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 3.5 / 17

Access Clarity 14.3 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 5.9 / 15

Agent readiness — 18/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 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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

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

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 github.com/api-evangelist/eko-health: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Medical Technology (certified health IT, FDA-authorized AI devices)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 2

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

Eko Health Storefront MCP

A live, anonymously reachable Model Context Protocol server published on Eko Health's own www.ekohealth.com host, implementing the Shopify storefront / Universal Commerce Protoc...

Eko Connect Enterprise SDK and API

Eko Connect is Eko Health's integration surface for telehealth vendors, telemedicine cart makers, and life-science partners. It ships as native Android and iOS SDKs plus a REST ...

MCP Servers 1

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

Eko Health MCP Server

Remote MCP server at www.ekohealth.com over HTTP; 5 tools listed.

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Eko Health Plans

5 plans

PLANS

Security Posture 3

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

Eko Health Authentication

oauth2/openIdConnect/undocumented · 3 schemes

SECURITY

Eko Health Domain Security

TLSv1.3 · DMARC

SECURITY

Eko Health Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Eko Health Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgentSkill

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Conventions

Conventions

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 6

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Compliance

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 1

Properties that don't map to a standard resource type

OpenIDConnect

OpenIDConnect

Source (apis.yml)

aid: eko-health
name: Eko Health
description: 'Eko Health Inc. is an Oakland, California digital health company that builds FDA-cleared digital stethoscopes
  (CORE 500, CORE Digital Attachment, DUO, and the 3M Littmann CORE) together with cloud software and AI algorithms for the
  detection of cardiovascular and pulmonary disease. Its platform pairs the hardware with the Eko App (iOS/Android), the Eko
  web Dashboard, Eko AI murmur/AFib/low-ejection-fraction detection, and SENSORA, an enterprise AI cardiac disease detection
  platform for health systems. For integrators Eko publishes Eko Connect — an Enterprise SDK and API surface that live-streams
  auscultation audio and single-lead ECG into third-party telehealth, telemedicine cart, and life-science applications. The
  Enterprise SDK and its backing REST API at api.ekodevices.com are commercially gated: there is no public developer portal,
  OpenAPI, or self-serve documentation, and access is arranged through Eko sales. The company''s public agent-facing surface
  is its Shopify storefront, which serves a live anonymous MCP server, an agents.md / llms.txt, and Universal Commerce Protocol
  discovery.'
url: https://raw.githubusercontent.com/api-evangelist/eko-health/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
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: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - security
  generated: '2026-09-02'
  method: derived
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-10-06'
image: https://www.ekohealth.com/cdn/shop/files/eko-logo_1.svg?v=1743130101&width=500
tags:
- Company
- Health
- Healthcare
- Medical Devices
- Digital Health
- Telehealth
- Artificial Intelligence
- Cardiology
- Remote Patient Monitoring
- Commerce
apis:
- aid: eko-health:eko-storefront-mcp
  name: Eko Health Storefront MCP
  description: 'A live, anonymously reachable Model Context Protocol server published on Eko Health''s own www.ekohealth.com
    host, implementing the Shopify storefront / Universal Commerce Protocol (UCP) shopping service. A tools/list call returns
    five real tools with full JSON input schemas: search_catalog, get_product_details, get_cart, update_cart, and search_shop_policies_and_faqs.
    The store also publishes an agents.md (mirrored at /llms.txt), a UCP merchant profile at /.well-known/ucp, and OAuth/OIDC
    discovery documents that expose the customer-account-mcp-api:full scope. The parallel UCP MCP endpoint at /api/ucp/mcp
    requires an agent profile URI and returns a 422 UCP discovery failure without one.'
  humanURL: https://www.ekohealth.com/agents.md
  baseURL: https://www.ekohealth.com/api/mcp
  tags:
  - MCP
  - Commerce
  - Agents
  properties:
  - type: MCPServer
    url: mcp/eko-health-mcp.yml
  - type: LLMsTxt
    url: llms/eko-health-llms.txt
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: storefront-mcp
- aid: eko-health:eko-connect
  name: Eko Connect Enterprise SDK and API
  description: 'Eko Connect is Eko Health''s integration surface for telehealth vendors, telemedicine cart makers, and life-science
    partners. It ships as native Android and iOS SDKs plus a REST API hosted at api.ekodevices.com that carries auscultation
    recordings, live audio/ECG streaming, and dashboard data. The service is real and live — an unauthenticated GET of /api/v1/recordings
    returns HTTP 401 — but the contract is commercially gated: Eko publishes no developer portal, no OpenAPI or Swagger document,
    and no self-serve documentation at any of the probed hosts, so integrators obtain the SDK and credentials through Eko
    sales. Its component health (Enterprise SDK, Enterprise SDK EAS, Enterprise SDK Livestream, Eko Dashboard, Eko Livestream,
    Eko Video) is published on the Eko status page.'
  humanURL: https://www.ekohealth.com/pages/telehealth-integrations
  baseURL: https://api.ekodevices.com
  tags:
  - SDK
  - Telehealth
  - Streaming
  - Medical Devices
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.ekohealth.com/blogs/newsroom
  type: Blog
- url: https://www.ekohealth.com/blogs/newsroom.atom
  type: BlogRSS
- type: DomainSecurity
  url: security/eko-health-domain-security.yml
- type: Website
  url: https://www.ekohealth.com/
- type: Support
  url: https://support.ekohealth.com/hc/en-us
- type: Blog
  url: https://www.ekohealth.com/blogs/eko-blog
- type: GitHubOrganization
  url: https://github.com/EkoDevices
- type: Pricing
  url: https://www.ekohealth.com/pages/software
- type: SignUp
  url: https://account.ekohealth.com/
- type: TermsOfService
  url: https://support.ekohealth.com/hc/en-us/articles/13156765697563-Terms-of-Service
- type: PrivacyPolicy
  url: https://support.ekohealth.com/hc/en-us/articles/13156748616731-Privacy-Policy
- type: StatusPage
  url: https://status.ekohealth.com/
- type: Security
  url: https://support.ekohealth.com/hc/en-us/articles/13156748752155-Security-and-HIPAA
- type: Compliance
  url: https://support.ekohealth.com/hc/en-us/articles/13156748752155-Security-and-HIPAA
- type: VulnerabilityDisclosure
  url: security/eko-health-vulnerability-disclosure.yml
- type: WellKnown
  url: well-known/eko-health-well-known.yml
- type: Authentication
  url: authentication/eko-health-authentication.yml
- type: OAuthScopes
  url: scopes/eko-health-scopes.yml
- type: OpenIDConnect
  url: well-known/eko-health-openid-configuration.json
- type: Conformance
  url: conformance/eko-health-conformance.yml
- type: Lifecycle
  url: lifecycle/eko-health-lifecycle.yml
- type: Conventions
  url: conventions/eko-health-conventions.yml
- type: Packages
  url: packages/eko-health-packages.yml
- type: Plans
  url: plans/eko-health-plans.yml
- type: MCPServer
  url: mcp/eko-health-mcp.yml
- type: LLMsTxt
  url: llms/eko-health-llms.txt
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 21
  pass: local-v1

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/eko-health"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/eko-health/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.