# CMS DMEPOS Supplier Payments Scraper API (`pink_comic/cms-dmepos-supplier-utilization-payments`) Actor

Search CMS annual Medicare DMEPOS supplier utilization and payment aggregates by NPI, supplier, geography, specialty, volume, payment, and DME/POS/drug component.

- **URL**: https://apify.com/pink\_comic/cms-dmepos-supplier-utilization-payments.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Business, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 cms dmepos supplier payments scraper api evidence items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CMS DMEPOS Supplier Payments Scraper API

Search the official public CMS **Medicare DMEPOS supplier utilization and payment aggregate** dataset by supplier NPI, organization/person name, state, ZIP, specialty, entity type, utilization/payment thresholds, and DME, POS, or drug component. Results are source-linked, bounded, and shaped for supplier research, market analysis, and claims-utilization workflows.

### Deterministic first run

```json
{"supplierNPI":"1003000399","maxResults":1,"scanLimit":1}
```

This returns the verified annual aggregate row for **Reconstructive Hand To Shoulder Of Indiana, LLC**, including geography, specialty, beneficiaries, claims, services, submitted charges, allowed amounts, Medicare payments, standardized payments, and DME/POS/drug breakdowns.

Pricing is **$0.0001 per start + $0.002 per dataset item**. The default produces at most one item, so its maximum charge is **$0.0021**. A buyer-set maximum total charge reduces `maxResults` before paging.

### Inputs

- `supplierNPI`: exact 10-digit NPI (server-side CMS filter)
- `query`: organization/person-name substring
- `state`, `zip`, `specialty`, `entityType` (`O` or `I`)
- `minBeneficiaries`, `minClaims`, `minServices`, `minMedicarePayment`
- `componentType`: `ALL`, `DME`, `POS`, or `DRUG`
- `sortBy`: `supplierName`, `beneficiaries`, `claims`, `services`, or `medicarePayment`
- `sortDirection`, `scanLimit` (up to 5,000), and total `maxResults` (up to 500)

Broad local filtering and sorting examine only `scanLimit` source rows. Every result discloses the candidate count and whether that bound applied.

### Output and provenance

Stable output includes supplier identity/address/specialty, aggregate totals, DME/POS/drug subtotals, selected beneficiary demographics and risk score, suppression indicators, dataset ID, exact source URL, retrieval timestamp, scan disclosure, and explicit `FOUND`, `NO_MATCH`, `SOURCE_UNAVAILABLE`, or `INVALID_INPUT` outcomes.

Source dataset ID: `a2d56d3f-3531-4315-9d87-e29986516b41`.

### Evidence boundaries

This is **annual claims-derived aggregate evidence**, not a live transaction feed. CMS privacy suppression is material: blank/suppressed cells remain `null` and appear in `suppressedFields`; they are never converted to zero. Snapshot/claims-year coverage can lag and CMS may revise aggregates.

A record does **not** establish Medicare enrollment, licensure, ownership, current activity, identity, fraud or its absence, quality, medical necessity, reimbursement eligibility, payment entitlement, or real-time payment. A no-match does not prove that a supplier does not exist or had no activity. Use PECOS/licensing and other appropriate primary sources for consequential determinations.

# Actor input Schema

## `supplierNPI` (type: `string`):

Optional exact supplier npi filter or result-control setting. See the README for source semantics and examples.

## `query` (type: `string`):

Optional supplier name filter or result-control setting. See the README for source semantics and examples.

## `state` (type: `string`):

Optional state filter or result-control setting. See the README for source semantics and examples.

## `zip` (type: `string`):

Optional zip filter or result-control setting. See the README for source semantics and examples.

## `specialty` (type: `string`):

Optional exact cms specialty filter or result-control setting. See the README for source semantics and examples.

## `entityType` (type: `string`):

Optional entity type filter or result-control setting. See the README for source semantics and examples.

## `minBeneficiaries` (type: `integer`):

Optional minimum beneficiaries filter or result-control setting. See the README for source semantics and examples.

## `minClaims` (type: `integer`):

Optional minimum claims filter or result-control setting. See the README for source semantics and examples.

## `minServices` (type: `number`):

Optional minimum services filter or result-control setting. See the README for source semantics and examples.

## `minMedicarePayment` (type: `number`):

Optional minimum medicare payment (usd) filter or result-control setting. See the README for source semantics and examples.

## `componentType` (type: `string`):

Optional required component filter or result-control setting. See the README for source semantics and examples.

## `sortBy` (type: `string`):

Optional sort by filter or result-control setting. See the README for source semantics and examples.

## `sortDirection` (type: `string`):

Optional sort direction filter or result-control setting. See the README for source semantics and examples.

## `scanLimit` (type: `integer`):

Bounded candidate scan before local filters and sorting.

## `maxResults` (type: `integer`):

Total paid dataset items. Default 1 costs at most $0.0021 including start.

## Actor input object example

```json
{
  "supplierNPI": "1003000399",
  "entityType": "",
  "minBeneficiaries": 0,
  "minClaims": 0,
  "minServices": 0,
  "minMedicarePayment": 0,
  "componentType": "ALL",
  "sortBy": "medicarePayment",
  "sortDirection": "desc",
  "scanLimit": 1,
  "maxResults": 1
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "supplierNPI": "1003000399",
    "scanLimit": 1,
    "maxResults": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/cms-dmepos-supplier-utilization-payments").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "supplierNPI": "1003000399",
    "scanLimit": 1,
    "maxResults": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/cms-dmepos-supplier-utilization-payments").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "supplierNPI": "1003000399",
  "scanLimit": 1,
  "maxResults": 1
}' |
apify call pink_comic/cms-dmepos-supplier-utilization-payments --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pink_comic/cms-dmepos-supplier-utilization-payments"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/cfDhMUgaojEkVGLFm/builds/3B0Y00nFe9qWctd2r/openapi.json