CMS — Centers for Medicare & Medicaid Services
The Centers for Medicare & Medicaid Services (CMS) is the U.S. federal agency within the Department of Health and Human Services that administers Medicare, Medicaid, the Children's Health Insurance Program (CHIP), the Health Insurance Marketplace, and the broader CMS open-data program. CMS operates one of the largest collections of HL7 FHIR APIs in the U.S. federal government — Blue Button 2.0, BCDA, AB2D, DPC, and the upstream BFD server — alongside the Marketplace API, the data.cms.gov open-data catalog, the Provider Data Catalog, the Quality Payment Program API, and the Medicare Coverage Database.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles CMS — Centers for Medicare & Medicaid Services the way a machine reads it — 50 machine-readable artifacts across 25 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — CMS — Centers for Medicare & Medicaid Services scores 47.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile CMS — Centers for Medicare & Medicaid Services
Each block below is one kind of artifact we hold for CMS — Centers for Medicare & Medicaid Services. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 25
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
CMS — Centers for Medicare & Medicaid Services Articles API
The Articles API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for articles.
CMS — Centers for Medicare & Medicaid Services Auth API
The Auth API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for auth.
CMS — Centers for Medicare & Medicaid Services Benchmarks API
The Benchmarks API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for benchmarks.
CMS — Centers for Medicare & Medicaid Services Bulk Export API
The Bulk Export API from CMS — Centers for Medicare & Medicaid Services — 10 operation(s) for bulk export.
CMS — Centers for Medicare & Medicaid Services Catalog API
The Catalog API from CMS — Centers for Medicare & Medicaid Services — 4 operation(s) for catalog.
CMS — Centers for Medicare & Medicaid Services Coverage API
The Coverage API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for coverage.
CMS — Centers for Medicare & Medicaid Services Data API
The Data API from CMS — Centers for Medicare & Medicaid Services — 4 operation(s) for data.
CMS — Centers for Medicare & Medicaid Services Drugs API
The Drugs API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for drugs.
CMS — Centers for Medicare & Medicaid Services Eligibility API
The Eligibility API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for eligibility.
CMS — Centers for Medicare & Medicaid Services ExplanationOfBenefit API
The ExplanationOfBenefit API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for explanationofbenefit.
CMS — Centers for Medicare & Medicaid Services Geography API
The Geography API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for geography.
CMS — Centers for Medicare & Medicaid Services Group API
The Group API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for group.
CMS — Centers for Medicare & Medicaid Services Issuers API
The Issuers API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for issuers.
CMS — Centers for Medicare & Medicaid Services LCD API
The LCD API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for lcd.
CMS — Centers for Medicare & Medicaid Services Measurements API
The Measurements API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for measurements.
CMS — Centers for Medicare & Medicaid Services MEDCAC API
The MEDCAC API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for medcac.
CMS — Centers for Medicare & Medicaid Services Metadata API
The Metadata API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for metadata.
CMS — Centers for Medicare & Medicaid Services NCD API
The NCD API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for ncd.
CMS — Centers for Medicare & Medicaid Services Organization API
The Organization API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for organization.
CMS — Centers for Medicare & Medicaid Services Patient API
The Patient API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for patient.
CMS — Centers for Medicare & Medicaid Services Plans API
The Plans API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for plans.
CMS — Centers for Medicare & Medicaid Services Practitioner API
The Practitioner API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for practitioner.
CMS — Centers for Medicare & Medicaid Services Providers API
The Providers API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for providers.
CMS — Centers for Medicare & Medicaid Services Scoring API
The Scoring API from CMS — Centers for Medicare & Medicaid Services — 1 operation(s) for scoring.
CMS — Centers for Medicare & Medicaid Services Submissions API
The Submissions API from CMS — Centers for Medicare & Medicaid Services — 2 operation(s) for submissions.
Scroll within the panel for all 25 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
CMS AB2D API
OPEN COLLECTIONCMS Beneficiary Claims Data API (BCDA)
OPEN COLLECTIONCMS Beneficiary FHIR Data Server (BFD)
OPEN COLLECTIONCMS Blue Button 2.0 API
OPEN COLLECTIONCMS Data at the Point of Care API (DPC)
OPEN COLLECTIONCMS Marketplace API
OPEN COLLECTIONCMS Medicare Coverage Database API
OPEN COLLECTIONCMS Open Data API (data.cms.gov)
OPEN COLLECTIONCMS Provider Data Catalog API
OPEN COLLECTIONCMS Quality Payment Program API
OPEN COLLECTIONScroll within the panel for all 10 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Cms Gov Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cms Gov Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Cms Gov Bcda Job Example
EXAMPLECms Gov Patient Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for CMS — Centers for Medicare & Medicaid Services — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cms-gov · machine-readable index on apis.io