JenaValve Technology, Inc. is a privately held medical-device company headquartered at 4 Cromwell, Irvine, California, with an EU headquarters in the Central Tower, Landsberger Str. 110, Munich and a UK office at Unit 9A Astley Way, Swillington, Leeds. Founded in 2006 on a concept developed in 1995 by Professors Hans Figulla and Markus Ferrari, it develops the Trilogy Heart Valve System, a transcatheter aortic valve replacement (TAVR) device purpose-built for the minimally invasive treatment of severe aortic regurgitation (AR) as well as aortic stenosis (AS), delivered transfemorally and transapically with a porcine pericardial valve. The system carries a CE mark and is an investigational device in the United States, supported by the ALIGN-AR and ARTIST clinical studies and the JENA-VAD registry. The company has raised roughly $364 million across 13 rounds from investors including Bain Capital Life Sciences, the Qatar Investment Authority, Pictet Alternative Advisors, Innovatus Capital Partners and Peijia Medical. JenaValve operates no developer API programme — there is no developer portal, no API documentation, no keys, no SDKs, no CLI, no MCP server, no agent card, no changelog and no status page, and no developer, api, docs, status or trust subdomain resolves. Its two corporate WordPress sites do each serve an anonymously readable REST API, and on both of them the standard content collections are wide open while the administrative routes are correctly locked to 401.
JenaValve Technology publishes 7 APIs on the APIs.io network, including Authors API, Content API, Discovery API, and 4 more. Tagged areas include Company, Medical Devices, Healthcare, Cardiology, and Structural Heart.
JenaValve Technology’s developer surface includes engineering blog, product news, support, documentation, authentication, and 23 more developer resources.
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/.
aid: jenavalve-technology
name: JenaValve Technology
description: JenaValve Technology, Inc. is a privately held medical-device company headquartered at 4 Cromwell, Irvine, California,
with an EU headquarters in the Central Tower, Landsberger Str. 110, Munich and a UK office at Unit 9A Astley Way, Swillington,
Leeds. Founded in 2006 on a concept developed in 1995 by Professors Hans Figulla and Markus Ferrari, it develops the Trilogy
Heart Valve System, a transcatheter aortic valve replacement (TAVR) device purpose-built for the minimally invasive treatment
of severe aortic regurgitation (AR) as well as aortic stenosis (AS), delivered transfemorally and transapically with a porcine
pericardial valve. The system carries a CE mark and is an investigational device in the United States, supported by the
ALIGN-AR and ARTIST clinical studies and the JENA-VAD registry. The company has raised roughly $364 million across 13 rounds
from investors including Bain Capital Life Sciences, the Qatar Investment Authority, Pictet Alternative Advisors, Innovatus
Capital Partners and Peijia Medical. JenaValve operates no developer API programme — there is no developer portal, no API
documentation, no keys, no SDKs, no CLI, no MCP server, no agent card, no changelog and no status page, and no developer,
api, docs, status or trust subdomain resolves. Its two corporate WordPress sites do each serve an anonymously readable REST
API, and on both of them the standard content collections are wide open while the administrative routes are correctly locked
to 401.
image: https://jenavalve.com/wp-content/uploads/cropped-jvicon.png
url: https://raw.githubusercontent.com/api-evangelist/jenavalve-technology/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline-2026-08-04
x-sector: medical-devices
x-api-posture: no-product-api
specificationVersion: '0.20'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Medical Devices
- Healthcare
- Cardiology
- Structural Heart
- TAVR
- Aortic Regurgitation
- Aortic Stenosis
- Heart Valves
- Clinical Trials
- Patient Education
- Private Company
apis:
- aid: jenavalve-technology:jenavalve-technology-authors-api
name: JenaValve Technology Authors API
description: Public author profiles attached to published content.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- Authors
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-authors-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-content-api
name: JenaValve Technology Content API
description: The AR education library — posts, pages and site search.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- Content
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-content-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-discovery-api
name: JenaValve Technology Discovery API
description: Route and capability discovery documents.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- Discovery
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-discovery-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-media-api
name: JenaValve Technology Media API
description: Uploaded media library items.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- Media
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-media-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-oembed-api
name: JenaValve Technology O Embed API
description: oEmbed provider endpoint for discover-ar.com URLs.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- oEmbed
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-oembed-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-seo-api
name: JenaValve Technology SEO API
description: Yoast SEO head-metadata endpoint.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- SEO
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-seo-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- aid: jenavalve-technology:jenavalve-technology-taxonomy-api
name: JenaValve Technology Taxonomy API
description: The articles / videos / audio / presentations category taxonomy.
humanURL: https://jenavalve.com/news/
baseURL: https://jenavalve.com/wp-json
tags:
- Taxonomy
properties:
- type: OpenAPI
url: openapi/jenavalve-technology-taxonomy-api-openapi.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Overlay
url: overlays/jenavalve-technology-discover-ar-overlay.yaml
- type: Website
url: https://jenavalve.com/
- type: About
url: https://jenavalve.com/about-us/
- type: Blog
url: https://jenavalve.com/news/
- type: News
url: https://jenavalve.com/news/
- type: Support
url: https://jenavalve.com/contact/
- type: Contact
url: https://jenavalve.com/contact/
- type: Careers
url: https://jenavalve.com/careers/
- type: Investors
url: https://jenavalve.com/investors/
- type: Product
url: https://jenavalve.com/trilogy-system/
- type: Documentation
url: https://eifu.jenavalve.com/
- type: Resources
url: https://discover-ar.com/
- type: ClinicalTrials
url: https://jenavalve.com/align-ar/
- type: TermsOfService
url: https://jenavalve.com/terms-of-use/
- type: PrivacyPolicy
url: https://jenavalve.com/privacy-policy/
- type: CodeOfConduct
url: https://jenavalve.com/integrity-and-compliance/
- type: LinkedIn
url: https://www.linkedin.com/company/jenavalve
- type: SecondaryMarket
url: https://forgeglobal.com/jenavalve-technology_stock/
- type: WellKnown
url: well-known/jenavalve-technology-well-known.yml
- type: DomainSecurity
url: security/jenavalve-technology-domain-security.yml
- type: Authentication
url: authentication/jenavalve-technology-authentication.yml
- type: Conventions
url: conventions/jenavalve-technology-conventions.yml
- type: Conformance
url: conformance/jenavalve-technology-conformance.yml
- type: Lifecycle
url: lifecycle/jenavalve-technology-lifecycle.yml
- type: DataModel
url: data-model/jenavalve-technology-data-model.yml
- type: ErrorCatalog
url: errors/jenavalve-technology-problem-types.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
url: llms/jenavalve-technology-llms.txt
x-enrichment:
date: '2026-08-04'
status: enriched
artifacts_added: 15
pass: local-v1
notes: 'No product API. Contract discovery probed jenavalve.com, discover-ar.com and eifu.jenavalve.com for OpenAPI on each
host root, GraphQL, MCP tools/list, A2A agent cards at both the canonical and legacy well-known paths, and the full /.well-known/
set — every one 404 on the two WordPress hosts. eifu.jenavalve.com is a Next.js SPA on the third-party ifucare.io platform
whose catch-all answers 200 with an identical 2,454-byte HTML shell for every path including both agent-card paths; those
were recorded as false positives, not hits, and no agent card was written. The real machine-readable contracts are the
two anonymous WordPress REST APIs — jenavalve.com/wp-json (12 namespaces, 242 routes) and discover-ar.com/wp-json (8 namespaces,
197 routes). Their access posture is the inverse of the hardened WordPress pattern: every standard wp/v2 content collection
is wide open anonymously while the administrative routes correctly 401 (wp/v2/settings, block-types, menu-items, wp-abilities,
wp-site-health, CookieYes) and Contact Form 7 403s. Two OpenAPI 3.1 documents were derived from the route indexes plus
direct probing of every described operation — 24 verified anonymous operations on the main site, 18 on Discover AR. The
one genuinely editorial signal across both is Discover AR''s category taxonomy, which segments the aortic-regurgitation
education library by media format (articles 4, videos 6, audio 3, presentations 0). Searched and found no VDP, no bug
bounty, no trust center, no named security or privacy certification, no GitHub org, no packages, no CLI, no MCP server,
no changelog, no status page, no webhook or event surface, and no developer/api/docs/status/trust subdomain resolving.
Those artifacts were deliberately not written rather than stubbed. Domain security probe found TLS 1.3 on both hosts but
no HSTS, no DNSSEC and no CAA on either, DMARC at p=none on jenavalve.com and no DMARC at all on discover-ar.com. No idempotency
contract exists, so no Idempotency pointer was emitted; likewise no StatusPage, Deprecation, Security, Compliance, SDKs,
Postman, MCPServer, Webhooks or AgentCard pointer, because none of those things exist. The Integrity and Compliance page
is a Code of Conduct plus an EthicsPoint helpline with no named certification, so it is wired as CodeOfConduct rather
than Compliance.'
Kin Score
How this is scored →