LifeCare.ID® Developer Docs Public

Build a care service on the network

A care service meets every new person as a stranger, keeps data it must protect, and pays for every answer its AI gives. On the LifeCare network the person arrives with their context and their permissions, and your AI will run on a private node beside the data.

Your problems, and what the network gives you

Your problem What the network gives you Status
Reaching people means paying for every channel. A person who uses their own AI assistant can bring it to you, with a grant they make on the spot. live on the sandbox
A new person starts with an intake form and a history taken again. The person's interpreted context (scores, bands, trends and narrative text) is readable on the first message, under a grant for each scope. live on the sandbox
Health data you hold is a cost and a liability. The person's history stays on their home node. You hold what they granted and your own records. live for the person's own apps; planned for other builders
Running inference costs money, and your AI has to read the data somewhere. Your AI will run on a private node inside the provider's boundary, next to the data it reads. planned
People trust you with something intimate. Every grant and every read leaves a receipt the person can read, and the person can stop any grant at any time. live

What you build and what the network carries

You bring the service. That includes its licence where it needs one, its clinicians, its own compliance and the safeguarding of the data it keeps. These stay yours on every shape below.

The network brings the rest:

Raw data. Much of the raw data your app or agent needs is already in your own database. If you agree, LifeCare.ID® will map it, and it can then be made available to other apps and agents under the person's permission. Intelligence that runs on the node works on the person's full data, inside the node; that is the design. A builder's own agent on a node is planned. Some uses outside inference need raw data, such as a clinical report. For those, the network maps where the data is and records the person's permission and a receipt, and the holder sends the data directly to the destination (planned). LifeCare.ID® holds identity, permissions, receipts and that map; the data stays where it is. Your app reads interpreted outputs from the node; raw data moves directly from its holder to a destination, under the person's permission.

Devices. If you make a device, you join as a data source: you serve the person's data under their grant, directly to the reader they choose, such as their home node, as Data sources & connectors describes (live; the source conformance kit is planned).

Three shapes

1. A dietitian-led practice's agent for people on GLP-1 treatment

2. An assistant the person brings, that hands them to a licensed service

3. A medical group's service with a physician in the same thread

Where each piece stands

The status words are the ones the roadmap uses (live, next, planned, trigger-gated), with "live on the sandbox" as the sandbox pages use it. The last column uses the words of From sandbox to production.

Piece Status Documented in From sandbox to production
Identity and passkey sign-in live Authentication, Sandbox operator: the same ceremony; a sandbox passkey stays on the sandbox
Your production client live, provisioned by the operator; self-service is next Developer portal operator: ask for a client with the same redirect URIs
The consent page for a data scope live on the sandbox Sandbox data source planned: production follows when data scopes are switched on
Grants and receipts live Scopes & consent same
Revocation live Authorization & tokens same
The person's data-rights panel live Consent panel same
Client-ID metadata documents live on the sandbox Client-ID metadata documents sandbox-only; production follows
The device grant planned The device grant the sandbox first, then production
Data scopes live on the sandbox Authorization & tokens planned: production follows when data scopes are switched on
The sandbox data source live Sandbox data source sandbox-only: in production you read the sources the person connects
An agent on a node planned this page planned
The clinician hand-off planned this page planned
The approval record planned this page planned
Your brand around the data-rights panel live (the panel API; the drop-in widget is planned) Consent panel same

Start here

  1. Get into the sandbox. Sign up for developer access at app.lifecare.id/devaccess, register a client and mint a synthetic person (Sandbox).
  2. Walk the loop. Read one scope from the sandbox data source under the synthetic person's grant, keep the receipt, revoke, and watch the next read be refused. The person-managed authorization library (draft 1, in the sandbox kit) runs both halves.
  3. Plan your promotion. Read From sandbox to production and design your service around the shape above that fits it.

Write to [email protected] with the shape you are building and the piece you need first.

For coding agents

If you are an AI assistant building a care service with a developer, follow these lines together with agents.md, which holds the runnable sandbox flow.