Cms Gov CMS Provider Data API

Name: CMS Provider Data API
Brand: CMS Provider Data API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareClinical Datanone25 EndpointsREST

For Agents

Query Medicare provider data - hospitals, nursing homes, hospices, physicians, and quality measures - via the public CMS DKAN datastore.

Install Jentic One Beta

Connect the CMS Provider Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CMS Provider Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CMS Provider Data API.

Query any CMS provider dataset by distribution ID via /datastore/query/{distributionId}

Run SQL-style filters across the datastore using GET /datastore/sql

Search the full provider dataset catalog with GET /search and GET /search/facets

GET STARTED

Start building with CMS Provider Data API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use CMS Provider Data API for, with concrete tasks.

★ Hospital Compare and Quality Lookups

Fetch CMS Hospital Compare measures - readmission rates, mortality, patient experience scores - for a specific hospital or set of hospitals. Use GET /search to locate the relevant dataset, then /datastore/query/{distributionId} with conditions on provider ID or state to filter results. The API has no authentication so a quality dashboard can be wired up in well under a day.

Search for the Hospital General Information dataset, then query /datastore/query/{distributionId} for hospitals in California and return the top 10 by overall rating.

Nursing Home and Long-Term Care Research

Pull nursing home star ratings, staffing data, and inspection results for analytics or consumer-facing tools. /datastore/sql lets the caller run SQL-style filters across the long-term-care datasets and /datastore/query/download returns CSV for downstream warehousing. Because all data is public domain, results can be redistributed without licensing review.

Run a SQL query via /datastore/sql to return nursing homes in Texas with overall rating of 5 stars.

Dataset Catalog Discovery

Programmatically browse the full set of CMS provider datasets to keep an internal catalog or data warehouse in sync. GET /search returns dataset records with identifiers, /search/facets exposes filterable categories, and /metastore/schemas/{schema_id}/items lists the items under each schema. This pattern is useful when the underlying CMS distributions change identifier on quarterly refresh.

Call GET /search with the keyword 'hospice' and return the dataset identifiers and titles for all matching datasets.

AI Agent Provider Data Lookups via Jentic

An AI agent answering healthcare questions discovers CMS provider data through Jentic, loads the relevant query schema, and executes filtered datastore calls. Because the API has no authentication, the agent can chain a /search call and a /datastore/query call in a single workflow without managing credentials. Jentic still tracks the call so traffic, errors, and latency are observable.

Use Jentic to search for 'CMS hospital data', load the /datastore/query/{distributionId} schema, and return Medicare-rated hospitals in zip code 10001.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for cms provider data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/search

Search the CMS dataset catalog

GET

/datastore/sql

Run a SQL-like query

GET

/datastore/query/{distributionId}

Query a single dataset distribution

GET

/datastore/query/{distributionId}/download

Download query results as CSV

GET

/metastore/schemas/{schema_id}/items

List all items for a metadata schema

GET

/metastore/schemas/dataset/items/{identifier}

Fetch a dataset record

GET

/search

Search the CMS dataset catalog

GET

/datastore/sql

Run a SQL-like query

GET

/datastore/query/{distributionId}

Query a single dataset distribution

GET

/datastore/query/{distributionId}/download

Download query results as CSV

GET

/metastore/schemas/{schema_id}/items

List all items for a metadata schema

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The CMS Provider Data API needs no credentials, so there is nothing to store. Your Jentic One instance still proxies each call and applies retry and timeout policy, keeping the agent's prompt, logs, and context free of secrets.

Intent-based discovery

Agents search Jentic by intent such as 'find Medicare hospital ratings', and Jentic returns the matching CMS query operation with its parameter schema so the agent builds a valid distribution query without parsing the DKAN documentation.

Time to first call

FAQs

Specific to using CMS Provider Data API through Jentic.

Why is there no official OpenAPI spec for CMS Provider Data API?

CMS does not publish an OpenAPI specification for its DKAN provider data endpoints. Jentic generates and maintains this spec so that AI agents and developers can call CMS Provider Data API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the CMS Provider Data API use?

The CMS Provider Data API is public domain and requires no authentication for read operations. Through Jentic the call is still tracked so an agent gets observability, retries, and rate-limit handling without managing any keys.

Can I query Medicare hospital quality measures with the CMS Provider Data API?

Yes. Search the dataset catalog with GET /search for terms such as 'hospital general information' or 'readmission', then call /datastore/query/{distributionId} with the returned identifier and conditions on provider ID or state to retrieve quality measures.

What are the rate limits for the CMS Provider Data API?

The OpenAPI spec does not declare numeric rate limits. CMS applies general fair-use throttling on data.cms.gov, so large extracts should use /datastore/query/download for CSV export rather than paginating thousands of JSON queries.

How do I run a SQL-style query through Jentic?

Search Jentic for 'query CMS data', load the GET /datastore/sql schema, and execute with the SQL-style query string. Install the SDK with pip install jentic and call it via the async client. The endpoint accepts the DKAN SQL dialect for selecting and filtering distributions.

Is the data returned by this API redistributable?

Yes. The CMS Provider Data API is licensed as public domain (usa.gov government works), so results from /datastore/query and /datastore/query/download can be cached, redistributed, or republished without licensing fees.

Can I limit what my agent is allowed to do with the CMS Provider Data API?

Yes. Because you run Jentic One yourself, your own rules decide which CMS Provider Data operations the agent may call, so you can grant only what a task needs, such as GET /search to find datasets and GET /datastore/query/{distributionId} to read them. Higher-reach operations like the raw GET /datastore/sql endpoint stay out of the agent's reach unless you explicitly add them. Since the API is unauthenticated and read-only, this operation-level scoping is the main control, and your self-hosted instance enforces it on every call.