Every plan's benefits, premiums, and county footprint in one clean API — plus market intelligence that shows exactly where plan exits leave members shopping for new coverage.
Free tier included · No credit card to start · REST + MCP for AI agents
CMS publishes the data as thousands of coded fields across a dozen file formats. We ingest, decode, and join all of it so you can just ask.
Copays, coinsurance, deductibles, and limits for every category — synthesized into human-readable cost sharing, from primary care to inpatient stays.
County-exact plan availability with local premiums from the CMS Landscape files, including regional and national plans.
Side-by-side comparison of up to five plans: premiums, copays, Rx deductibles, star ratings, membership, and extra benefits.
Real membership per plan and per county from the CMS monthly enrollment files — know exactly how big every plan actually is.
What happened to any plan year over year: renewed, consolidated, terminated, or new — including dead plan IDs your clients ask about.
A hosted MCP server lets Claude and other AI tools search plans, compare benefits, and pull market reports natively.
Every January, plans terminate or leave counties — and their members must choose new coverage. Our reports join the CMS crosswalk, landscape, and enrollment files to size that opportunity, county by county.
No sales call, no onboarding queue.
Sign up and get an API key instantly. The free tier is real — enough to build and evaluate.
REST endpoints for plans, benefits, comparisons, and market reports — or connect your AI agent over MCP.
Point your agents at the counties where displaced members are already shopping.
Every tier includes the full dataset — benefits, enrollment, and market reports. Tiers differ only in monthly request volume.
Everything is built from public CMS releases: Plan Benefit Package (PBP) files, the annual Landscape files, the Part C&D Plan Crosswalk, and the monthly enrollment by contract/plan/state/county. We decode the raw codes into human-readable benefits.
When a plan terminates or pulls out of a county, its members must actively choose new coverage during enrollment. Our reports join the crosswalk, landscape, and enrollment files to count those members in every county — and verify each "consolidation" against the destination year's real service area, so you're not chasing phantom opportunities.
Yes — a hosted MCP (Model Context Protocol) server ships with every account, so Claude and other AI tools can search plans, compare benefits, and pull market reports directly.
Plan benefits follow the CMS contract-year releases and multiple years stay live side by side. Enrollment refreshes from the CMS monthly files, and the crosswalk lands each fall for the coming plan year.
No. This is an independent product built on publicly available CMS data. It is not endorsed by or affiliated with CMS, medicare.gov, or the U.S. government, and it is not a source of enrollment advice for beneficiaries.
Free tier, instant API key, full dataset access.
Create your account →