# LifeCare.ID® developer documentation > Developer documentation for LifeCare.ID®, the patient-held identity, consent and authorization layer for health data that stores no health data: concepts, the trust model, getting started, the sandbox, the API reference and the published contract. LifeCare.ID® is built and operated by HCVC.net (Enbarca Inc), founded by Raphael Gernot. It is the consent layer under ProForta (https://proforta.com/) and the Healthspan Node (https://github.com/enbarca/healthspannode). Partner pages (authentication, onboarding, scopes and consent, tokens, the consent panel, agent trust, data sources, the developer portal) need a developer account or a partner code and are not listed here. ## Public pages - [LifeCare.ID® developer documentation](https://developers.lifecare.id/): Build on a patient-controlled identity, consent, and authorization layer for health data that stores no health data, ever. - [Trust model](https://developers.lifecare.id/trust-model): Four mechanisms carry every trust claim LifeCare.ID® makes, and each one has a canonical reference page on lifecare.id that states it against the implementation serving the network today, over a published, drift-tested... - [Concepts](https://developers.lifecare.id/concepts): Everything you need to reason about a LifeCare.ID® integration. If you read one page before coding, read this one. - [You can't be deplatformed: a developer's bill of rights](https://developers.lifecare.id/bill-of-rights): The short version. On a Web2 platform, the platform owns your users and can cut you off. On LifeCare.ID®, nobody owns the user, the user owns themselves. - [Getting started (relying-party app)](https://developers.lifecare.id/getting-started): This walks a brand-new application from zero to reading consented data. It assumes you're building an app (a requester). If you're building a data source, start at Data sources & connectors instead. - [Sandbox](https://developers.lifecare.id/sandbox): Engage with LifeCare.ID® without requesting access. The sandbox is an isolated instance where you self-register an app and mint a synthetic signed-in user in seconds, then run the full sign-in to grant to token to... - [From sandbox to production](https://developers.lifecare.id/sandbox-to-production): The sandbox matches production except where it must: the same handlers, the same tokens, the same receipt, with synthetic people and self-service in place of real members and an operator. - [Sandbox data source](https://developers.lifecare.id/sandbox-data-source): The sandbox gives you identities, grants and tokens. This page is the other half: a data source that honours those tokens, so an app or an agent has something to read under consent. - [Client-ID metadata documents: how the issuer admits an agent](https://developers.lifecare.id/client-id-metadata): Status: the policy on this page is ruled (D-AI3, 2026-11-05). The LifeCare.ID® issuer accepts client-ID metadata documents under these rules on the sandbox (live, AI-SANDBOX-CIMD), and production follows (gated,... - [The device grant: how an agent with no browser asks](https://developers.lifecare.id/device-grant): Status: ruled (D-AI11, 2026-11-05). The LifeCare.ID® issuer will offer the device authorization grant (RFC 8628) for an agent that cannot host a redirect. This note comes first. - [Build a care service on the network](https://developers.lifecare.id/build-a-care-service): A care service meets every new person as a stranger, keeps data it must protect, and pays for every answer its AI gives. - [Recipes](https://developers.lifecare.id/recipes): Task-oriented guides, copy, adapt, ship. Each is self-contained and links to the deeper reference. For full runnable apps, see the quickstarts. - [Building on LifeCare.ID® with a coding agent](https://developers.lifecare.id/for-coding-agents): Paste one file into your project's agent instructions and your coding agent builds on person-managed authorization with LifeCare.ID® by the rules, not by guessing. - [Person-managed authorization](https://developers.lifecare.id/person-managed-authorization): Person-managed authorization lets a person decide what an agent may read from a server, and stop it at any time, using the OAuth flow that MCP already follows. LifeCare.ID® is its first implementation. - [API reference](https://developers.lifecare.id/api-reference): The complete endpoint catalogue available today. This page is a human-readable companion to the machine-readable contract, the authoritative, drift-tested source is docs/contracts/openapi.json (regenerated on every API... - [Security & compliance](https://developers.lifecare.id/security-and-compliance): Integrating with LifeCare.ID® means inheriting, and upholding, a small set of hard guarantees. This page states what the platform guarantees you, and what you must guarantee in return. - [Procurement & compliance pack](https://developers.lifecare.id/procurement-and-compliance): For security reviewers, privacy officers, and procurement teams evaluating an integration that uses LifeCare.ID®. The goal of this page is to let you clear review before your engineers write code. Share it freely. - [Roadmap](https://developers.lifecare.id/roadmap): What's live, what's next, and what's further out, so you can build with confidence and design toward what's coming. - [Developer terms](https://developers.lifecare.id/terms): Placeholder. This is a short, good-faith stub so the access flow can ship. It is not final legal text and is not legal advice; HCVC will have counsel review and replace it before relying on it. Version: 2026-09-02. ## For coding agents - [agents.md](https://developers.lifecare.id/agents.md): one paste-ready file of instructions for a coding agent building on person-managed authorization with LifeCare.ID®: the rules, the map, the sandbox flow as runnable steps and the checks that mean done. Also served at /AGENTS.md, as text/markdown. - [Building on LifeCare.ID® with a coding agent](https://developers.lifecare.id/for-coding-agents): what to paste, why, and how the file stays true. ## Try it - [Sandbox](https://sandbox.lifecare.id/.well-known/openid-configuration): the isolated instance where an app self-registers and mints a synthetic signed-in user; synthetic, zero-PHI data only. - [Sandbox synthetic source](https://lifecare.id/sandbox-source): the reference data source that honours sandbox tokens; its JSON description lists the personas, the scopes and the endpoints. - [The published API contract](https://developers.lifecare.id/openapi.json): the OpenAPI document the service is drift-tested against. ## Elsewhere - [lifecare.id](https://lifecare.id/llms.txt): the product site, in the same format, with the reference pages (consent receipt, authorization server, zero egress, attestation) and the paper (DOI 10.5281/zenodo.22855810). - [proforta.com](https://proforta.com/llms.txt): the first app on the consent layer. - [LifeCare.ID® on Substack](https://lifecare.substack.com/): writing on patient data sovereignty and the architecture of trust.