# Regency Healthcare

**Canonical:** https://apis.io/providers/regencyhealthcare/  
**Website:** https://regencyhealthcare.in  
**APIs profiled:** 0

Regency Healthcare is a multi-specialty tertiary and super-speciality hospital network in northern India, operating five centres across Kanpur, Lucknow and Gorakhpur with 240+ doctors and physicians covering 20+ medical specialties including cardiology, oncology (cancer care), nephrology, orthopedics and gastroenterology. Patient-facing services include appointment booking, emergency and ambulance care, diagnostic imaging (PET-CT), and an online lab-report portal. Surfaced as a portfolio lead of norwest-venture-partners and added to the API Evangelist network; the enrichment pipeline found no public developer/API surface for this provider.

## Kin Score — 3.3 / 100 (minimal)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.0 from 3.3).

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

Regulatory layer — **Health**: 7.5 (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 |

## Access

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

## Security (1)

- **Regencyhealthcare Domain Security** — TLSv1.3 · HSTS · DMARC

## Tags

Company, Healthcare, Hospitals, Medical, Health, India, Patient Care

---

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