consolidate.health is built with Framer, hosted on AWS behind Cloudflare. It measures traffic with Google Analytics and Google Tag Manager. It sends email through HubSpot (Marketing Hub tracking & forms) and Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| 3.0.1 | 9 Nov 2026 | |
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management4 | ||
| – | 9 Nov 2026 | |
| Advertising & Affiliate Tracking1 | ||
| – | 9 Nov 2026 | |
| Email Marketing & Lead Capture1 | ||
| – | 9 Nov 2026 | |
| Transactional Email1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
| Security, WAF & Bot Protection1 | ||
| – | 9 Nov 2026 | |
| Translation & Localization1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comns-1316.awsdns-36.orgns-97.awsdns-12.comns-548.awsdns-04.netns-1916.awsdns-47.co.ukgoogle-site-verification=AnzFASGhuPTVOtV2kibpzQEz_CxFeLwuJHTOvef5PV0google-site-verification=nNrokMq0a5WjNSNFLmozf8zV-Wmny6QzLkvU_ejC82Uv=spf1 include:amazonses.com include:_spf.google.com include:243377565.spf03.hubspotemail.net -allatlassian-domain-verification=qIuDCMqsydhJ640pLaUwyNeWfQAEDaIPgrZqcuY6DTijIjHFmwYI72iKINH6nxeBgoogle-site-verification=_3bbSMFunHZVug_pt_g3XBSjbpUVn4Fp9sKPZArWX8Ianthropic-domain-verification-ww1nak=MgaabxlnaspSv3tlow83IarMfv=DMARC1; p=reject; pct=100; rua=mailto:dmarc@consolidate.health; adkim=r; aspf=rUser-agent: * Allow: / Sitemap: https://consolidate.health/sitemap.xml
# 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.
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – | 9 Nov 2026 |