# CMS Open Payments API — Physician Roll-up (Sunshine Act) (`malonestar/cms-open-payments`) Actor CMS Open Payments (Sunshine Act) API: look up physician or manufacturer general payments by name, NPI or manufacturer, rolled up per physician × manufacturer — total USD, payment count, date range and payment-type mix. Pharma-compliance ready. Keyless, official CMS. - **URL**: https://apify.com/malonestar/cms-open-payments.md - **Developed by:** [Kyle Maloney](https://apify.com/malonestar) (community) - **Categories:** Lead generation, Developer tools, Automation - **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.40 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use 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 Open Payments API — Physician × Manufacturer Roll-up (Sunshine Act) A **CMS Open Payments (Sunshine Act) API**: look up **physician** or **manufacturer** general payments by name, **NPI**, or manufacturer, and roll them up **per physician × manufacturer** — total USD, payment count, date range, and payment-type mix. Turn millions of disclosure rows into a compliance-ready summary. Keyless, official CMS source. ### Who it's for - **Pharma / medtech compliance** teams auditing physician payment exposure. - **Investigative & policy researchers** analyzing industry-to-physician money. - **Healthcare due-diligence & journalists** profiling a physician or maker. - **AI agents** needing a "look up Open Payments" tool. ### What it does Queries CMS Open Payments general payments by physician (name / NPI / profile ID) or manufacturer, then aggregates each physician × manufacturer pair into one row: total dollars, number of payments, first/last payment dates, and a breakdown by payment type (consulting, food & beverage, travel, etc.). Optional specialty enrichment. ### Example input ```json { "lastName": "smith", "firstName": "john", "programYear": "2023", "includeSpecialty": true, "maxResults": 200 } ```` ### Output (per physician × manufacturer) `physician_name`, `npi`, `specialty`, `manufacturer`, `total_amount_usd`, `payment_count`, `first_payment_date`, `last_payment_date`, and `payment_type_mix`. ### Use as an MCP tool Available to AI agents via `mcp.apify.com` as an "Open Payments lookup" tool — name or NPI in, rolled-up payment summary out. ### FAQ **What is Open Payments / the Sunshine Act?** CMS's public record of payments from drug & device makers to physicians. **Can I search by NPI?** Yes — by name, NPI, or profile ID, or by manufacturer. **Is it aggregated?** Yes — rolled up per physician × manufacturer. **Is it keyless?** Yes, official CMS source. ### Source **openpaymentsdata.cms.gov** (DKAN2 datastore, paginated at 500/req). Official, keyless. ### Pricing (Pay Per Result) Billed per roll-up record returned. Empty searches cost nothing. # Actor input Schema ## `lastName` (type: `string`): Covered-recipient (physician) last name to search for. Case-insensitive substring match. Combine with firstName to narrow. Leave blank to search by NPI or manufacturer only. ## `firstName` (type: `string`): Covered-recipient (physician) first name. Case-insensitive substring match. Best used together with lastName. ## `npi` (type: `string`): Exact 10-digit National Provider Identifier of the physician. The most precise way to look up one physician's payments. ## `profileId` (type: `string`): Exact CMS Open Payments covered-recipient profile ID, if you already have it (an alternative precise physician key to NPI). ## `manufacturer` (type: `string`): Name (or part of the name) of the drug/device manufacturer or GPO making the payment. Case-insensitive substring match. Use alone to profile a manufacturer, or with a physician filter to narrow to one relationship. ## `programYear` (type: `string`): Reporting year to query, e.g. 2024. Leave blank to automatically use the most recent General Payments dataset published by CMS. ## `includeSpecialty` (type: `boolean`): When on, look up each physician's specialty from the NPPES NPI registry when the payment record lacks one. Best-effort; never fails the run. ## `maxResults` (type: `integer`): Upper bound on raw payment rows fetched (in pages of 500) before aggregating. NOTE: CMS paginates via SQL OFFSET, which slows sharply past ~2000 rows; a time budget stops very deep pulls and returns partial results. Narrow the filter (add firstName/NPI/manufacturer) for complete deep results. ## Actor input object example ```json { "lastName": "Smith", "includeSpecialty": false, "maxResults": 500 } ``` # Actor output Schema ## `results` (type: `string`): Physician x manufacturer payment rollups, in the default dataset. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "lastName": "Smith", "maxResults": 500 }; // Run the Actor and wait for it to finish const run = await client.actor("malonestar/cms-open-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "lastName": "Smith", "maxResults": 500, } # Run the Actor and wait for it to finish run = client.actor("malonestar/cms-open-payments").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "lastName": "Smith", "maxResults": 500 }' | apify call malonestar/cms-open-payments --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=malonestar/cms-open-payments", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "CMS Open Payments API — Physician Roll-up (Sunshine Act)", "description": "CMS Open Payments (Sunshine Act) API: look up physician or manufacturer general payments by name, NPI or manufacturer, rolled up per physician × manufacturer — total USD, payment count, date range and payment-type mix. Pharma-compliance ready. Keyless, official CMS.", "version": "1.0", "x-build-id": "VIPbYOXZVOZKWGe2l" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/malonestar~cms-open-payments/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-malonestar-cms-open-payments", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/malonestar~cms-open-payments/runs": { "post": { "operationId": "runs-sync-malonestar-cms-open-payments", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/malonestar~cms-open-payments/run-sync": { "post": { "operationId": "run-sync-malonestar-cms-open-payments", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "lastName": { "title": "Physician last name", "type": "string", "description": "Covered-recipient (physician) last name to search for. Case-insensitive substring match. Combine with firstName to narrow. Leave blank to search by NPI or manufacturer only." }, "firstName": { "title": "Physician first name", "type": "string", "description": "Covered-recipient (physician) first name. Case-insensitive substring match. Best used together with lastName." }, "npi": { "title": "Physician NPI", "type": "string", "description": "Exact 10-digit National Provider Identifier of the physician. The most precise way to look up one physician's payments." }, "profileId": { "title": "Covered recipient profile ID", "type": "string", "description": "Exact CMS Open Payments covered-recipient profile ID, if you already have it (an alternative precise physician key to NPI)." }, "manufacturer": { "title": "Manufacturer / GPO name", "type": "string", "description": "Name (or part of the name) of the drug/device manufacturer or GPO making the payment. Case-insensitive substring match. Use alone to profile a manufacturer, or with a physician filter to narrow to one relationship." }, "programYear": { "title": "Program year", "type": "string", "description": "Reporting year to query, e.g. 2024. Leave blank to automatically use the most recent General Payments dataset published by CMS." }, "includeSpecialty": { "title": "Enrich physician specialty via NPPES", "type": "boolean", "description": "When on, look up each physician's specialty from the NPPES NPI registry when the payment record lacks one. Best-effort; never fails the run.", "default": false }, "maxResults": { "title": "Max payment rows to pull before roll-up", "minimum": 1, "maximum": 100000, "type": "integer", "description": "Upper bound on raw payment rows fetched (in pages of 500) before aggregating. NOTE: CMS paginates via SQL OFFSET, which slows sharply past ~2000 rows; a time budget stops very deep pulls and returns partial results. Narrow the filter (add firstName/NPI/manufacturer) for complete deep results.", "default": 2000 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```