# ConKay Medical Systems

**Canonical:** https://apis.io/providers/conkay-medical-systems/  
**Website:** https://www.conkaymedical.com/  
**APIs profiled:** 1

ConKay Medical Systems is an early‑stage medical device company focused on developing minimally invasive solutions to treat valvular regurgitation in patients with progressive heart failure. Founded in 2020 and based in Pleasanton, CA, the company advances annular repair catheter systems for the tricuspid valve, aiming to reduce the need for open‑heart surgery.

## Kin Score — 5.6 / 100 (minimal)

Scored 2026-11-06 under rubric 0.27.0. Trend: flat (-0.1 from 5.7).

| Facet | Score |
|---|---|
| Discoverability | 67.0 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Access Clarity | 0.0 |

Regulatory layer — **Health**: 4.7 (matched via tags).

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |
| MCP Tool Quality | na |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## APIs (1)

- **ConKay API** — ConKay Medical Systems API (no public documentation found)

## Security (1)

- **Conkay Medical Systems Domain Security** — TLSv1.3 · HSTS

## Tags

Medical Devices, Cardiovascular, Valvular Regurgitation, Early Stage, Pleasanton

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/conkay-medical-systems/). Scores are computed from the provider's own public artifacts under a published rubric.