AdjuCor GmbH
AdjuCor GmbH is a Munich, Germany medical device company, founded in 2012, that develops reBEAT — an implantable, patient-specific cardiac support system for advanced heart failure. reBEAT is an epicardial device that conforms to the outside of the heart and delivers uni- or biventricular mechanical circulatory support without ever contacting blood, which is intended to avoid the thrombosis, stroke and haemolysis risks that constrain conventional blood-pumping ventricular assist devices. It is implanted on the beating heart in a minimally invasive, suture-free procedure by a heart team. The company reported first-in-human implantations in 2023 and runs an EIC co-funded EU project toward market entry; the device remains investigational. AdjuCor is a hardware manufacturer rather than a software business, and publishes no developer program, public API, SDK, or machine-readable API contract on any host it operates.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles AdjuCor GmbH 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 — AdjuCor GmbH scores 7.6/100 (minimal), 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
AdjuCor GmbH builds an implantable cardiac support device (reBEAT) in Munich and sells hardware to heart teams, not software to developers: its entire public surface is a seven-page WordPress marketing site (home, technology, team, news, contact, privacy policy) with no developer, docs, portal, API or integration link anywhere in the nav, footer or page source, and that WordPress router answers every non-page path — including a random control path — with the same 2,679-byte "WordPress > Error" page under HTTP 500, so /openapi.json, /swagger.json, /api-docs, /llms.txt, /wp-json/, /?rest_route=/ and every /.well-known/ path are all hard misses; api., docs., developer., developers., portal., app., data. and connect..adjucor.com do not resolve in DNS at all, there is no adjucor GitHub organization (404) and no package named adjucor on npm or PyPI. The one subdomain that does resolve, cloud.adjucor.com, is a login-walled self-hosted Nextcloud 25.0.3 appliance — third-party software AdjuCor runs internally, not an API it publishes — whose only served /.well-known/ document is Nextcloud's own vendor-default security.txt pointing at hackerone.com/nextcloud and expired 2023-04-30, so it is recorded as a miss rather than credited to AdjuCor.
This is an honest zero, not a gap in our research. AdjuCor GmbH 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://adjucor.com/→ HTTP 200https://adjucor.com/openapi.json→ HTTP 500https://adjucor.com/swagger.json→ HTTP 500https://adjucor.com/api-docs→ HTTP 500https://adjucor.com/llms.txt→ HTTP 500https://adjucor.com/wp-json/→ HTTP 500https://adjucor.com/?rest_route=/→ HTTP 500https://adjucor.com/developers→ HTTP 500https://adjucor.com/.well-known/agent-card.json→ HTTP 500https://adjucor.com/.well-known/agent.json→ HTTP 500https://adjucor.com/.well-known/api-catalog→ HTTP 500https://adjucor.com/.well-known/security.txt→ HTTP 500https://adjucor.com/zz-api-evangelist-control-9f3a→ HTTP 500https://cloud.adjucor.com/.well-known/agent-card.json→ HTTP 404https://cloud.adjucor.com/.well-known/security.txt→ HTTP 200https://api.github.com/orgs/adjucor→ HTTP 404
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-07 · rubric v0.20.0
Put this on your own site. The badge is drawn live from AdjuCor GmbH'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/adjucor/"
title="AdjuCor GmbH on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/adjucor.svg"
alt="AdjuCor GmbH Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/adjucor/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/adjucor/"
title="AdjuCor GmbH on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/adjucor/card.svg"
alt="AdjuCor GmbH 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 AdjuCor GmbH
Each block below is one kind of artifact we hold for AdjuCor GmbH. 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 AdjuCor GmbH — 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.
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
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/adjucor · machine-readable index on apis.io
This is an independent, third-party profile of AdjuCor GmbH, 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.