Exo website screenshot

Exo

Exo (Exo Imaging, Inc.) is a Santa Clara, California medical imaging company building a handheld ultrasound ecosystem for point-of-care ultrasound (POCUS). Its silicon-based Exo Iris handheld probe pairs an FDA-cleared, on-device AI suite (SweepAI, cardiac and lung assessment, hemodynamics indicators) with Exo Works, an AWS-hosted POCUS workflow, documentation, billing, QA and credentialing platform. Exo Works is device-agnostic and connects to hospital systems over DICOM (modality worklist, PACS/VNA) and HL7 (ADT, ultrasound orders, exam results), with SAML single sign-on and Active Directory. Exo publishes no public developer API, OpenAPI, SDK or developer portal; its integration surface is the DICOM/HL7 interface engine documented for hospital IT, and its production API host (api.prod.exoworks.inc) is private to the Exo Works clients.

Exo is profiled on the APIs.io network. Tagged areas include Company, Health, Healthcare, Medical Imaging, and Ultrasound.

Exo’s developer surface includes documentation, getting-started guide, support, engineering blog, pricing, authentication, changelog, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub
36.1/100 thin ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
0 APIs
CompanyHealthHealthcareMedical ImagingUltrasoundPoint of CareArtificial IntelligenceMedical DevicesDICOMHL7

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 36.1/100 · thin
Contract Quality 0.0 / 21
Developer Ergonomics 6.3 / 17
Commercial Clarity 15.7 / 17
Operational Transparency 2.3 / 11
Governance 1.3 / 10
Discoverability 4.9 / 9
Regulatory Posture 5.6 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 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
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.
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/. This rating is computed from github.com/api-evangelist/exo: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Pricing Plans 1

Published pricing tiers and plan structures.

Exo Plans

11 plans

PLANS

Security Posture 3

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

Exo Authentication

saml/ldap/password/mfa/biometric · 5 schemes

SECURITY

Exo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Exo Trust Center

HITRUST, SOC 2 Type II, ISO 27001, ISO 27701, HIPAA, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted
GettingStarted
 Login
Login

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 Lifecycle
Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 TrustCenter
TrustCenter
 Compliance
Compliance
 Authentication
Authentication
 TrustCenter
TrustCenter

Operate 2

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 3

The organization behind the API

Website
Website
 Blog
Blog
 Careers
Careers

Other 2

Properties that don't map to a standard resource type

Investments
Investments
 EventCatalog
EventCatalog

Source (apis.yml)

apis.yml Raw ↑ 
aid: exo
name: Exo
description: Exo (Exo Imaging, Inc.) is a Santa Clara, California medical imaging company building a handheld ultrasound ecosystem
  for point-of-care ultrasound (POCUS). Its silicon-based Exo Iris handheld probe pairs an FDA-cleared, on-device AI suite
  (SweepAI, cardiac and lung assessment, hemodynamics indicators) with Exo Works, an AWS-hosted POCUS workflow, documentation,
  billing, QA and credentialing platform. Exo Works is device-agnostic and connects to hospital systems over DICOM (modality
  worklist, PACS/VNA) and HL7 (ADT, ultrasound orders, exam results), with SAML single sign-on and Active Directory. Exo publishes
  no public developer API, OpenAPI, SDK or developer portal; its integration surface is the DICOM/HL7 interface engine documented
  for hospital IT, and its production API host (api.prod.exoworks.inc) is private to the Exo Works clients.
image: https://images.ctfassets.net/f1onadsih6xk/2h0Ji7EHg7lS6RQLWyECpx/ddb89eb356079629033488b6424535ed/home-resized.png
url: https://raw.githubusercontent.com/api-evangelist/exo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.20'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Health
- Healthcare
- Medical Imaging
- Ultrasound
- Point of Care
- Artificial Intelligence
- Medical Devices
- DICOM
- HL7
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/exo-domain-security.yml
- type: Website
  url: https://www.exo.inc/
- type: Documentation
  url: https://support.exo.inc/hc/en-us
- type: GettingStarted
  url: https://support.exo.inc/hc/en-us/sections/22799151240603-Sign-In
- type: Support
  url: https://www.exo.inc/contact
- type: Blog
  url: https://www.exo.inc/newsroom
- type: GitHubOrganization
  url: https://github.com/exo-imaging
- type: Pricing
  url: https://store.exo.inc/
- type: Login
  url: https://cloud.exoworks.inc/
- type: TermsOfService
  url: https://store.exo.inc/policies/terms-of-service
- type: PrivacyPolicy
  url: https://www.exo.inc/privacy-policy
- type: TrustCenter
  url: https://www.exo.inc/security-trust-center
- type: Compliance
  url: https://www.exo.inc/security-trust-center/security
- type: Investments
  url: https://www.exo.inc/investors
- type: Careers
  url: https://www.exo.inc/careers
- type: Authentication
  url: authentication/exo-authentication.yml
- type: Conformance
  url: conformance/exo-conformance.yml
- type: Lifecycle
  url: lifecycle/exo-lifecycle.yml
- type: ChangeLog
  url: changelog/exo-changelog.yml
- type: Plans
  url: plans/exo-plans.yml
- type: LLMsTxt
  url: llms/exo-llms.txt
- type: EventCatalog
  url: events/exo-iris-activity-events.yml
- type: TrustCenter
  url: security/exo-trust-center.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 10
  pass: local-v1