Medigate

Medigate was a healthcare IoT / connected-medical-device cybersecurity company (headquartered in Brooklyn, NY, backed by Partech and others) that built the first security platform dedicated to healthcare IoT — device discovery, risk assessment, and clinically-aware network segmentation for hospitals. Claroty completed its acquisition of Medigate on 2022-01-10 and folded the product into "Claroty xDome for Healthcare"; the standalone brand is retired and medigate.io now redirects to claroty.com. A residual customer-facing REST API remains live at api.medigate.io (with a password-gated interactive reference at api.medigate.io/docs) that integrations use to pull device inventory, device groups, and device risk scores.

Medigate publishes 1 API on the APIs.io network. Tagged areas include Company, Infrastructure Saas, Cybersecurity, Healthcare, and Medical Devices.

Medigate’s developer surface includes API reference, authentication, and 8 more developer resources.

🌐 Visit website 📡 Source on GitHub

18.8/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Infrastructure Saas Cybersecurity Healthcare Medical Devices Internet of Things Device Security Network Security

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 18.8/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.6 / 17

Access Clarity 4.5 / 17

Operational Transparency 1.2 / 11

Contract Governance 0.0 / 10

Discoverability 5.8 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 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/medigate: 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 →

APIs 1

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

Medigate API

Customer-facing REST API for the Medigate (now Claroty xDome for Healthcare) device-security platform. Documents two versions — V1 (HTTP basic auth) and V2 (API token) — used to...

Security Posture 4

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

Medigate Authentication

http/apiKey · 2 schemes

SECURITY

Medigate Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Medigate Vulnerability Disclosure

disclosure policy published

SECURITY

Medigate Trust Center

SOC 2, ISO 27001, HIPAA, GDPR, CSA STAR

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

APIReference

APIReference

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Access & Security 6

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

TrustCenter

TrustCenter

Compliance

Compliance

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: medigate
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/medigate.png
name: Medigate
description: Medigate was a healthcare IoT / connected-medical-device cybersecurity company (headquartered in Brooklyn, NY,
  backed by Partech and others) that built the first security platform dedicated to healthcare IoT — device discovery, risk
  assessment, and clinically-aware network segmentation for hospitals. Claroty completed its acquisition of Medigate on 2022-01-10
  and folded the product into "Claroty xDome for Healthcare"; the standalone brand is retired and medigate.io now redirects
  to claroty.com. A residual customer-facing REST API remains live at api.medigate.io (with a password-gated interactive reference
  at api.medigate.io/docs) that integrations use to pull device inventory, device groups, and device risk scores.
url: https://raw.githubusercontent.com/api-evangelist/medigate/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
x-status: acquired
x-acquired-by: claroty
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Infrastructure Saas
- Cybersecurity
- Healthcare
- Medical Devices
- Internet of Things
- Device Security
- Network Security
apis:
- name: Medigate API
  description: Customer-facing REST API for the Medigate (now Claroty xDome for Healthcare) device-security platform. Documents
    two versions — V1 (HTTP basic auth) and V2 (API token) — used to pull the Device List, Device Groups, and device Risk
    scores. The interactive reference at api.medigate.io/docs is access-gated (password required), so no public OpenAPI is
    available.
  humanURL: https://api.medigate.io/docs
  baseURL: https://api.medigate.io
  properties:
  - type: Authentication
    url: authentication/medigate-authentication.yml
common:
- type: Website
  url: https://claroty.com/
- type: APIReference
  url: https://api.medigate.io/docs
- type: Authentication
  url: authentication/medigate-authentication.yml
- type: Lifecycle
  url: lifecycle/medigate-lifecycle.yml
- type: DomainSecurity
  url: security/medigate-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/medigate-vulnerability-disclosure.yml
- type: Security
  url: https://web-assets.claroty.com/team82-disclosure-policy.pdf
- type: TrustCenter
  url: security/medigate-trust-center.yml
- type: Compliance
  url: https://claroty.com/trust
- type: PrivacyPolicy
  url: https://claroty.com/privacy-policy
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 6
  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/medigate"

All providers

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

Every operation they expose

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

How their score was established

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