Developer access
DeepGarden APIPlanned
Canopy is for people with a question. The API is for people with a codebase. It is the same collected, normalized, entity-resolved data underneath — reached programmatically instead of through a workspace, so you can put it behind your own product, your own model or your own internal tooling.
DeepGarden API — programmatic access to the data
$ ▍
Illustrative. The API is planned, not shipped — the page below says exactly where it stands.
Why an API and not a file drop
Most published data is already downloadable. That has never been the hard part. The hard part is that identifiers change between releases, the same organization appears under six spellings, and a table that was fine last quarter has quietly gained two columns and lost a code system. Anyone building on raw public data spends most of their time maintaining a pipeline rather than building the thing they wanted to build.
What the API is meant to sell is the maintenance, not the bytes. Entities resolved once and kept resolved, identifiers crosswalked across years so a change in a number means a change in the world, and a schema that does not move under you without a version telling you it did.
What it would serve
The DeepGarden Data catalog: the maintained CMS Medicare Advantage datasets, with resolution across contracts, plans, parent organizations and counties, and crosswalks between release years.
Read-only, versioned, and scoped by key to the datasets a given licence covers — the same access model the platform already enforces internally, exposed rather than rebuilt.
Where this actually stands
Nothing here is built. This page exists because the data underneath it is real and maintained today, and because enough people have asked for it programmatically that it is worth saying out loud that we are considering it rather than pretending it already ships.
If you would use it, the useful thing you can tell us is which datasets, at what shape and what refresh cadence, and what you are building — that is what decides whether this gets built and in what order.
The same maintained data, reached from your own code. Tell us what you would build on it.
The rest of the system
the whole system, connected to your data
the enterprise intelligence workspace
where your data is given meaning
the governed data pipeline
analysis-ready external data products
your records, matched to the market
training, curriculum and advisory
the people who get it working and keep it working
DeepGarden under your brand, or inside your product
See it against your own numbers.
Bring a question your team cannot answer today and we will run it against data that looks like yours.