# Consolidate Health — Developer Platform

> Connect to patient health records via a normalized FHIR API. Get a sandbox in minutes,
> build and test with an AI tool against synthetic data, then request production access.

The MCP server and sandbox return SYNTHETIC data ONLY, in every environment — they are for
building and testing. Accessing REAL patient data (PHI) is done with your own app against the
direct Connect API under a signed contract; the AI agent is removed from that path. Production
access is never granted automatically — it requires a signed business agreement.

## Start here
- [Request sandbox access](https://onboarding.consolidate.health/request-access): Public form — email-verified; synthetic data plus a few real test seats.
- [Developer portal](https://onboarding.consolidate.health): Sign in once you have access — the API Reference, quickstart, SDKs, and MCP setup all live inside.
- [Connect an AI tool in one click (MCP)](https://mcp.consolidate.health): OAuth 2.1 remote MCP server — add the URL as a connector in ChatGPT/Claude, or in Cursor/Claude Code, then log in and consent (no keys to paste). You can create sandbox access right from the connect screen.

## API
- [OpenAPI spec](https://app.consolidate.health/api-spec): The Connect API spec, served when public API docs are enabled; otherwise use the API Reference inside the developer portal.
- [MCP OAuth discovery](https://onboarding.consolidate.health/.well-known/oauth-authorization-server): Authorization-server metadata — supports dynamic client registration, authorization_code, and PKCE.

## Production
- [Request production access](https://onboarding.consolidate.health): From inside the portal; our team follows up. Real patient data requires a signed contract and is accessed via the direct API, never through the MCP.

## Optional
- [Full guide for agents](https://onboarding.consolidate.health/llms-full.txt): Expanded, agent-oriented walkthrough — the exact one-click connect steps and the synthetic-only boundary in detail.