Abiomed
Abiomed is a Danvers, Massachusetts medical device manufacturer and, since December 22 2022, a standalone business inside Johnson & Johnson MedTech, which acquired it for approximately $16.6 billion. The company designs, manufactures and supports the Impella family of percutaneous micro-axial heart pumps — Impella CP, 5.5, RP Flex and the SmartAssist sensor line — used for temporary mechanical circulatory support during high-risk percutaneous coronary intervention and in cardiogenic shock, alongside the Automated Impella Controller console, the Breethe OXY-1 ECMO system and the Impella Connect remote case-review service. Its product is regulated hardware sold to hospitals and cath labs, supported by a 24/7 clinical support centre, not software sold to developers. Abiomed's digital surface is limited to two end-user products: Impella Connect, a customer-only clinician portal that receives one-way RTMPS video of the console screen over port 443, and the Impella App for clinical reference. Abiomed publishes no developer portal, no API reference, no OpenAPI or other machine-readable specification, no SDK on npm, PyPI or any other registry, and maintains no public source-code organisation; the corporate site abiomed.com now redirects to the brand site at heartrecovery.com.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Abiomed 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 — Abiomed scores 11.3/100 (emerging), 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
Abiomed sells regulated cardiac hardware — the Impella heart-pump family and its Automated Impella Controller console — and its only software is two end-user products with no developer surface: the customer-only Impella Connect clinician portal, whose Angular SPA catch-all answers HTTP 200 with the same HTML shell for /openapi.json, /swagger.json, /llms.txt and every /.well-known/* path, and the Impella App; abiomed.com 301s to www.heartrecovery.com, whose 375-URL sitemap contains no developer, API or integration page at all, api.impellaconnect.com is a private portal backend that answers every path with an nginx 502, and there is no SDK on npm or PyPI and no Abiomed-named GitHub organisation with a single public first-party repo.
This is an honest zero, not a gap in our research. Abiomed 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://www.heartrecovery.com/en-us→ HTTP 200https://www.heartrecovery.com/en-us/sitemap.xml→ HTTP 200https://www.heartrecovery.com/openapi.json→ HTTP 404https://www.heartrecovery.com/.well-known/api-catalog→ HTTP 404https://www.impellaconnect.com/openapi.json→ HTTP 200https://api.impellaconnect.com/openapi.json→ HTTP 502https://api.impellaconnect.com/api-docs→ HTTP 404https://api.github.com/orgs/Abiomed/repos→ 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-06 · rubric v0.19.0
Put this on your own site. The badge is drawn live from Abiomed'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/abiomed/"
title="Abiomed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/abiomed.svg"
alt="Abiomed Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/abiomed/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/abiomed/"
title="Abiomed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/abiomed/card.svg"
alt="Abiomed 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 Abiomed
Each block below is one kind of artifact we hold for Abiomed. 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 Abiomed — 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.
Get Started 1
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/abiomed · machine-readable index on apis.io
This is an independent, third-party profile of Abiomed, 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.