CMS Blue Button 2.0
Blue Button 2.0 is the Centers for Medicare & Medicaid Services (CMS) API that lets Medicare beneficiaries share their Parts A, B, and D claims data with applications they trust. It is a FHIR R4 API conforming to the CARIN Blue Button Implementation Guide (CARIN Consumer Directed Payer Data Exchange), serving ExplanationOfBenefit, Patient, and Coverage resources for 60+ million people with Medicare. Access is patient-facing - each beneficiary authorizes an app through an OAuth 2.0 authorization-code flow (with mandatory PKCE) on Medicare.gov, choosing whether to share demographic data. A self-serve sandbox with synthetic enrollee data is open to everyone; production credentials are free but require CMS approval of the application.
CMS Blue Button 2.0 publishes 5 API contracts indexed on the APIs.io network, including Coverage API, ExplanationOfBenefit API, Metadata API, and 2 more. Tagged areas include Blue Button, CARIN, Medicare, FHIR, and Claims Data.
The CMS Blue Button 2.0 catalog on APIs.io includes 1 Spectral governance ruleset.
CMS Blue Button 2.0’s developer surface includes authentication, documentation, sandbox, getting-started guide, and 11 more developer resources.
Kin Score
Standards implemented 3
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
CMS Blue Button 2.0 Coverage API
Medicare coverage resources, one per coverage type.
CMS Blue Button 2.0 ExplanationOfBenefit API
Medicare Parts A, B, and D claims as CARIN Blue Button EOB profiles.
CMS Blue Button 2.0 Metadata API
FHIR capability statement.
CMS Blue Button 2.0 Patient API
Beneficiary demographic and administrative data.
CMS Blue Button 2.0 User Info API
OpenID Connect userinfo for the authorizing beneficiary.
Open Collections 6
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
CMS Blue Button 2.0 Coverage API
OPEN COLLECTIONCMS Blue Button 2.0 Coverage ExplanationOfBenefit API
OPEN COLLECTIONCMS Blue Button 2.0 Coverage Metadata API
OPEN COLLECTIONCMS Blue Button 2.0 Coverage Patient API
OPEN COLLECTIONCMS Blue Button 2.0 Coverage UserInfo API
OPEN COLLECTIONCMS Blue Button 2.0 API
OPEN COLLECTIONCMS Blue Button 2.0 API pricing
Not yet checked against CMS Blue Button 2.0's own pricing page. Compiled by API Evangelist on 2026-07-11 from bluebutton.cms.gov/; confirm before you rely on a figure. A free plan or tier is listed.
| Plan | Price |
|---|---|
| Sandbox (Self-Serve) free | — |
| Production (CMS-Approved) free | — |
Plan details, limits and sources →
Rate limits
- API Request Rate: not published requests
- Access Token Lifetime: 1 hour time
- Refresh Token Use: 1 (one-time use) uses
Compiled by API Evangelist, not yet checked against CMS Blue Button 2.0's documentation. All 5 limits →
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
CMS Blue Button 2.0 Rate Limits
RATE LIMITSTerms of Service 1
What its API terms permit and prohibit, quoted from its own page.
CMS Blue Button 2.0
11 quoted statements, read from CMS Blue Button 2.0's own page on 2026-11-09.
TERMSEligibility 1
Who may sign up and where, quoted from its own terms.
CMS Blue Button 2.0
2 quoted statements, read from CMS Blue Button 2.0's own page on 2026-11-09.
ELIGIBILITYData License 1
How its data and outputs may be reused, quoted from its own terms.
CMS Blue Button 2.0
1 quoted statement, read from CMS Blue Button 2.0's own page on 2026-11-09.
LICENSEFinOps 1
Cost, billing, and metering signals for API financial operations.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
CMS Blue Button 2.0 API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access (API Evangelist recommendations) 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
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 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
CMS Blue Button 2.0 API — frequently asked questions
Does CMS Blue Button 2.0 have an API?
Yes. APIs.io lists 5 APIs from CMS Blue Button 2.0, including CMS Blue Button 2.0 Coverage API, CMS Blue Button 2.0 ExplanationOfBenefit API and CMS Blue Button 2.0 Metadata API, and 2 more.
Is there an OpenAPI specification for the CMS Blue Button 2.0 API?
Yes. APIs.io indexes 5 OpenAPI specifications for CMS Blue Button 2.0, each linked for download from this page.
How do I authenticate with the CMS Blue Button 2.0 API?
CMS Blue Button 2.0 documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as CMS Blue Button 2.0 Authentication.
How much does the CMS Blue Button 2.0 API cost?
APIs.io lists 2 pricing plans for CMS Blue Button 2.0, with each plan's price, limits and inclusions under Pricing on this page.
Is the CMS Blue Button 2.0 API ready for AI agents?
CMS Blue Button 2.0 has a Kin Score of 35.3 out of 100 (thin) and an Agent Readiness score of 28.4 (agent-aware), scored by API Evangelist on 2026-11-13.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.