# Eden Health > Eden Health was a primary and virtual care provider that delivered app-based > medical care, behavioral health, and care navigation to employers and their > employees (a healthcare company backed by Insight Partners). This llms.txt was > generated by the API Evangelist enrichment pipeline from the harvested backend > spec and repository artifacts; the company's public marketing site is no longer > reachable over TLS, but its "Grdn" (Guardian) backend still serves a Swagger 2.0 > description at api.edenhealth.com. ## API - [Grdn API (Swagger 2.0)](https://api.edenhealth.com/swagger.json): Eden Health's primary backend service — patients, appointments, membership, documents, care teams, and clinician tooling. Undocumented auth (a /v2/auth endpoint exists); URI-path versioned (v2). ## Specs - [Harvested OpenAPI/Swagger](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/openapi/eden-health-grdn-openapi-original.json) - [OpenAPI Overlay (our enhancements)](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/overlays/eden-health-grdn-overlay.yaml) ## Derived artifacts - [API conventions](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/conventions/eden-health-conventions.yml) - [Lifecycle & versioning](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/lifecycle/eden-health-lifecycle.yml) - [Data model / entity graph](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/data-model/eden-health-data-model.yml) - [Standards conformance](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/conformance/eden-health-conformance.yml) - [Agentic access contracts](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/agentic-access/eden-health-agentic-access.yml) - [Domain security probe](https://raw.githubusercontent.com/api-evangelist/eden-health/refs/heads/main/security/eden-health-domain-security.yml) ## Notes - The Grdn spec declares no operationIds, no component schemas, no securitySchemes, and only "default" responses, so MCP tools, Agent Skills, an error catalog, and an OAuth-scope/authentication profile are NOT derivable without fabrication and were intentionally skipped.