CMS Medicare Physician Fee Schedule Scraper
Pricing
from $33.75 / 1,000 records
CMS Medicare Physician Fee Schedule Scraper
Scrapes Medicare Physician Fee Schedule data from the CMS API. Returns rates, RVU components, and GPCI values for any HCPCS code, year, modifier, and locality.
Pricing
from $33.75 / 1,000 records
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
5 days ago
Last modified
Share
CMS Medicare Physician Fee Schedule Scraper
Scrape Medicare Physician Fee Schedule rates, RVUs, and GPCIs for any HCPCS code, year, and locality. Get the exact payment amount CMS publishes, with work, practice expense, and malpractice RVU components. Export to CSV, JSON, Excel, or XML.
CMS publishes the Medicare Physician Fee Schedule as a public data API, but querying it means building requests, handling pagination, and parsing nested JSON. This Actor reads that API directly and returns one flat row per code, year, modifier, and locality. You get the national rate or any of 112 geographic localities, for any year from 2000 to 2026.
| Who uses it | What they scrape CMS Medicare Physician Fee Schedule for |
|---|---|
| Medical billing companies | Which Medicare rate to expect for a specific code in a specific locality |
| Healthcare consultants | How RVU changes between years affect practice revenue |
| Revenue cycle managers | What the professional and technical component splits are for a code |
| Health economists | How geographic practice cost indices vary across the country |
| Practice administrators | Which codes are worth adding to a service line based on payment |
What it does
This Actor collects Medicare Physician Fee Schedule records by HCPCS/CPT code, year, modifier, and locality, and returns each one as a flat row with rates, RVU components, and GPCI values.
- 📋 Code lookup: Enter one or many HCPCS/CPT codes, or leave empty to export the entire fee schedule for a year.
- 📅 Year selection: Choose any year from 2000 to 2026, including the latest 2026 rates.
- 📍 Locality filter: Pick the national rate, a specific GPCI locality, or ALL localities for every code.
- 🔧 Modifier splits: Get the global base rate, professional component (26), technical component (TC), or discontinued procedure (53).
- 📊 Flat output: Each record is a single row with rate, RVU work, practice expense, malpractice, and GPCI values.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with CMS Medicare Physician Fee Schedule data
💰 Verify reimbursement rates.
A billing company enters a list of CPT codes and the locality for a client practice, then exports the exact Medicare allowable for each code to check against claims.
📈 Compare RVU changes year over year.
A healthcare consultant runs the Actor for the same codes across 2024, 2025, and 2026, then charts how work and practice expense RVUs shifted.
📍 Analyze geographic payment variation.
A health economist selects ALL localities for a set of high-volume codes and maps how the same service pays differently across the country.
🔧 Split professional and technical components.
A revenue cycle manager filters by modifier 26 and TC to see the separate payment for the physician and the facility for imaging codes.
📋 Build a fee schedule reference table.
A practice administrator exports the entire 2026 fee schedule for their state, then filters in a spreadsheet to create a quick reference for front-desk staff.
Why choose this scraper
| What you get | |
|---|---|
| No API coding | The Actor handles the CMS API request, pagination, and JSON parsing for you |
| Every year covered | Historical rates from 2000 through the current 2026 fee schedule |
| All localities | National rate plus 112 Medicare payment localities, or export all at once |
| Component splits | Global, professional, technical, and discontinued procedure rates in one run |
| Clean schema | One flat row per code, year, modifier, and locality, ready for analysis |
How it compares
No other Store actor targets CMS Medicare Physician Fee Schedule the same way, so the honest comparison is with the alternatives teams actually weigh.
| CMS Medicare Physician Fee Schedule Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When CMS Medicare Physician Fee Schedule changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor from HCPCS/CPT codes, fee schedule year, modifier, and geographic locality. Filters run as each record is read, so only matching codes and localities reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.045 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $4.50 |
| 1,000 results | $45.00 |
| 10,000 results | $450.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the CMS Medicare Physician Fee Schedule Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to CMS Medicare Physician Fee Schedule through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that the HCPCS codes are valid for the selected year. Some codes are added or removed over time. Also verify the locality code exists for that year. Try the national rate (0000000) to see if the code itself returns data.
The run is slow or times out.
If you are exporting all codes for all localities, the dataset can be very large. Reduce the maximum records, select a single locality, or narrow the year. The Actor paginates through the CMS API, so large exports take time.
I get an error about the API key.
The default API key is public and should work. If CMS changes it, you can update the API Access Key input. Contact support if the error persists.
The rates look different from what I expected.
Make sure you selected the correct year and locality. The national rate is unadjusted; local rates include GPCI adjustments. Also check the modifier: the global rate is different from the professional or technical component.
FAQ
| Question | Answer |
|---|---|
| What is the Medicare Physician Fee Schedule? | It is the list of payment rates CMS uses to reimburse physicians and other healthcare professionals for services covered under Medicare Part B. Each code has a relative value unit (RVU) that is multiplied by a conversion factor to get the dollar amount. |
| What are RVUs and GPCIs? | RVUs measure the relative work, practice expense, and malpractice cost of a service. GPCIs are geographic practice cost indices that adjust the national RVU for local cost differences. The Actor returns both. |
| Can I get rates for a specific year? | Yes. The year input accepts any year from 2000 to 2026. The default is 2026, the latest published fee schedule. |
| How do I look up a single CPT code? | Enter the code in the HCPCS / CPT Codes field, for example 99213. You can enter multiple codes separated by commas or spaces. Leave the field empty to export every code for the selected year. |
| What is the difference between global, professional, and technical components? | The global rate pays for the complete service. The professional component (modifier 26) pays only the physician work, and the technical component (modifier TC) pays only the equipment and staff. The Actor can return all of them or one. |
| What is a geographic locality? | Medicare divides the country into payment localities, each with its own GPCI. The Actor includes all 112 localities plus the national rate. You can pick one locality or export all of them for each code. |
| Does this Actor require an API key? | No. The Actor uses a public CMS data API key that is pre-filled. You do not need to register or provide your own key. |
| What output formats are supported? | The Actor exports to CSV, JSON, Excel, and XML. You choose the format when you run it on Apify. |
| Can I export the entire fee schedule for a year? | Yes. Leave the HCPCS / CPT Codes field empty and set the maximum records high enough. The Actor will paginate through the CMS API and return every code for that year and locality. |
| How many records can I get in one run? | The maximum records input lets you set a limit up to 1,000,000. The actual number depends on how many codes, years, and localities you select. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Centers for Medicare & Medicaid Services. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
