What data does the ProcedureRadar API return?

The ProcedureRadar API returns procedure prices from two federally mandated sources: hospital machine-readable files on every tier, and insurer-published Transparency in Coverage rates on Scale and above, in beta. Every pricing row carries a quality flag and source attribution. Rows backed by enough reporting hospitals add the cohort median, the sample size and percentiles where the sample supports them; a row with too few carries that hospital's posted price instead.

How do I authenticate with the ProcedureRadar API?

Pass your API key in the X-API-Key header on every request: X-API-Key: pr_live_... API keys are issued when you subscribe to any tier starting at $999/month, and free sandbox keys for evaluation are issued by email.

What endpoints does the ProcedureRadar API offer?

The API offers 7 endpoints: /v1/procedures for the procedure catalog; /v1/pricing for pricing rows by procedure and metro or hospital; /v1/hospitals for hospital details and transparency scores; /v1/hospitals/{id_or_slug} for one hospital with its full quality score breakdown; /v1/compare for side-by-side hospital pricing comparisons; /v1/payers for the insurers whose negotiated rates we serve; and /v1/metros for the metros your subscription covers.

ProcedureRadar API v1

Real Hospital Pricing Data. One REST Call.

Add real hospital pricing to your app this week. Quality-scored, source-attributed JSON from 2,000+ hospitals. No MRF parsing required.

Apply for API Access Book a 30-Minute Call Our Methodology

2,000+ hospitals

100 metros

Monthly refresh

Patent Pending

From $999/mo. 60-80% below enterprise APIs.

terminal

# Query MRI pricing in New York
curl "https://procedureradar.com/api/v1/pricing?procedure=mri-brain&metro=new-york" \
  -H "X-API-Key: pr_live_a1b2c3d4..."

# Response
{
  "data": [
    {
      "hospital_name": "Maimonides Medical Center",
      "procedure_slug": "mri-brain",
      "charge_type": "cash_discount",
      "median_price": 1210.00,
      "percentile_25": 870.00,
      "percentile_75": 1690.00,
      "sample_size": 38,
      "sample_regime": "full",
      "data_source": "hospital_mrf",
      "source_publication_date": "2026-09-15"
    }
  ]
}

# Query MRI pricing
curl "https://procedureradar.com/api/v1/pricing?procedure=mri-brain&metro=new-york" \
  -H "X-API-Key: pr_live_a1b2c3d4..."

# Response
{
  "data": [
    {
      "hospital_name": "Maimonides Medical Center",
      "procedure_slug": "mri-brain",
      "charge_type": "cash_discount",
      "median_price": 1210.00,
      "percentile_25": 870.00,
      "percentile_75": 1690.00,
      "sample_size": 38,
      "sample_regime": "full",
      "data_source": "hospital_mrf",
      "source_publication_date": "2026-09-15"
    }
  ]
}

The B2B API in one paragraph

Our B2B API gives mid-market payers, MGAs, TPAs, and insurtechs underwriting-grade procedure-pricing data. We source two federally mandated file types across 2,000-plus priced hospitals: hospital machine-readable files under 45 CFR Part 180, and payer-published Transparency in Coverage rates at Scale and above, from network-wide files, employer-group files and one single-employer file. Confidence intervals appear where samples support them.

The developer side of ProcedureRadar exists because we kept hearing the same thing from actuaries and product teams: the data is there, but nobody wants to parse it themselves. We do that part. Procedure pricing from more than 2,000 hospitals with published rates, with underwriting-grade fields where the sample size supports them, refreshed monthly and available via REST API. We get you set up on a quick call, then the keys are yours.
Kevin Monangai, Founder of ProcedureRadar

Base URLhttps://procedureradar.com/api/v1

Base URL

https://procedureradar.com/api/v1

Quickstart

From Approval to First Response in 15 Minutes

Three steps from approved account to live hospital pricing data in your application.Three steps from approved account to live pricing data.

Apply for Access

Submit an application at /signup/b2b. We review every application manually, usually within two business days. Once you are approved, we activate your account and send your API key by email. Prefer to talk it through first? Book a 30-minute call.Apply at /signup/b2b. Manual review, usually 2 business days. Once approved, we activate your account and email your key.

your-api-key

# Your key looks like this
pr_live_a1b2c3d4e5f6g7h8

Make Your First Request

Pass your key in the X-API-Key header and put the procedure and metro in the query string.Key in the X-API-Key header, procedure and metro in the query string.

request.sh

curl -X GET \
  "https://procedureradar.com/api/v1/pricing?procedure=mri-brain&metro=new-york" \
  -H "X-API-Key: pr_live_a1b2..."

Parse the Response

Rows come back in data[] with the source and its publication date, plus the cohort median and percentiles where the sample supports them.Rows come back in data[] with source, date, and median where supported.

response.json

{
  "data": [
    {
      "hospital_name": "Maimonides Medical Center",
      "procedure_slug": "mri-brain",
      "charge_type": "cash_discount",
      "median_price": 1210.00,
      "percentile_25": 870.00,
      "percentile_75": 1690.00,
      "sample_size": 38,
      "sample_regime": "full",
      "data_source": "hospital_mrf",
      "source_publication_date": "2026-09-15"
    }
  ]
}

Endpoints

Seven Endpoints, Two Federal Sources

All endpoints return JSON; pricing rows carry quality flags, sample sizes and source attribution.All return JSON; pricing rows carry quality flags and sources.

GET/v1/pricing

Query pricing rows by procedure and metro or hospital, optionally by payer type. Each row carries a quality flag and source attribution, plus the median, sample size and percentiles where the sample supports them.Pricing rows by procedure and metro or hospital: quality flag, source, and median and percentiles where supported.

proceduremetrohospital_idpayer_typepagelimit

GET/v1/hospitals

Look up hospital details and transparency scores. Filter by metro, state, or search by name.Look up hospital details and transparency scores. Filter by metro or state.

metrostatenamehas_pricing_datapagelimit

GET/v1/hospitals/{id_or_slug}

Retrieve one hospital by ID or slug with its full quality score breakdown and transparency rating.Retrieve one hospital by ID or slug with its full quality score breakdown.

id_or_slug

GET/v1/procedures

Browse the procedure catalog with display names, categories, and shoppable status. Search by keyword or filter by category.Browse the procedure catalog with display names, categories, and shoppable status.

categorysearchshoppable_onlypagelimit

GET/v1/compare

Compare pricing across hospitals for one procedure, side by side. Available on all paid tiers, scoped to the metros your tier covers.Compare pricing across hospitals for a procedure, side by side. All paid tiers.

hospitalsprocedurepayer_type

GET/v1/payers

List the insurers whose negotiated rates we serve, and the scope of each insurer's file.The insurers whose negotiated rates we serve.

GET/v1/metros

List the metros your subscription covers, with hospital counts and coverage status per metro.List the metros your subscription covers, with hospital counts per metro.

Authentication

API Key Authentication

Simple, standard, secure. One header on every request.

How It Works

Include your API key in the X-API-Key header of every request. We issue your key once we approve and activate your account.

Production Keys

Prefixed with pr_live_ for production. Counts against monthly quota.

Rate Limits

Per-minute and per-month limits vary by tier. Starter: 60/min, 25,000/mo. Growth: 300/min, 150,000/mo. Per-minute and per-month limits vary by tier. See all limits.

HTTPS Required

All API requests must use HTTPS. Plaintext HTTP requests are rejected with a 301 redirect.All requests must use HTTPS. HTTP is rejected with a 301 redirect.

authentication.sh

# Include your API key in the X-API-Key header
curl "https://procedureradar.com/api/v1/pricing?procedure=mri-brain&metro=new-york" \
  -H "X-API-Key: pr_live_a1b2c3d4..."

# Successful response: 200 OK
# Invalid key: 401 Unauthorized
# Rate limited: 429 Too Many Requests
# Tier restriction: 403 Forbidden

# HTTP Status Code Summary
# 200  Success
# 400  Bad Request (missing params)
# 401  Unauthorized (invalid key)
# 403  Forbidden (tier restriction)
# 429  Rate Limited
# 500  Server Error

Response Format

Every Response Includes

Structured, consistent, and fully attributed. No guesswork.Structured, consistent, fully attributed.

JSON by DefaultJSON by Default

Clean, predictable JSON structure on every endpoint. Consistent field naming across all responses. No XML, no CSV, no surprises.Clean, predictable structure. Consistent field naming across all endpoints.

Quality Flags and Sample SizesQuality Flags

Every pricing row carries a quality flag, the sample size behind it and a sample_regime field, so you can tell a backed percentile from a thin one.Every row carries a quality flag, sample size and sample_regime.

Source AttributionSource Attribution

Hospital name, source file and publication date on every pricing row, so your compliance team can trace each price to the federal filing it came from.Hospital name, MRF URL, and file date on every record. Full federal provenance.

Pagination for List EndpointsPagination

Page-based pagination with page and limit parameters and a total count in the pagination block. Default 25 rows per page, max 100.page and limit, total count included. Default 25, max 100.

full-response.json

{
  "success": true,
  "data": [
    {
      "tier": "growth",
      "hospital_id": "8f14e45f-ceea-467f-a8f5-1c1c2a3b4d5e",
      "hospital_name": "Maimonides Medical Center",
      "procedure_slug": "mri-brain",
      "procedure_display_name": "MRI Brain",
      "payer_id": null,
      "payer_name": null,
      "payer_scope": null,
      "payer_type": "cash",
      "charge_type": "cash_discount",
      "price": null,
      "gross_charge": null,
      "cash_pay": null,
      "median_price": 1210.00,
      "percentile_10": 640.00,
      "percentile_25": 870.00,
      "percentile_75": 1690.00,
      "percentile_90": 2380.00,
      "percentile_95": 2950.00,
      "percentile_99": 3610.00,
      "mean_price": 1342.50,
      "stdev_price": 512.30,
      "ci_lower_bound": 1105.00,
      "ci_upper_bound": 1318.00,
      "confidence_lower_p25": 790.00,
      "confidence_upper_p25": 948.00,
      "confidence_lower_p75": 1560.00,
      "confidence_upper_p75": 1822.00,
      "confidence_lower_p95": 2640.00,
      "confidence_upper_p95": 3260.00,
      "confidence_lower_p99": 3150.00,
      "confidence_upper_p99": 4070.00,
      "sample_size": 38,
      "quality_flag": "verified",
      "sample_regime": "full",
      "last_updated": "2026-10-01T00:00:00.000Z",
      "source_mrf_url": "https://example-hospital.org/standard-charges.csv",
      "source_publication_date": "2026-09-15",
      "data_source": "hospital_mrf",
      "setting": "outpatient",
      "billing_class": "facility",
      "methodology_url": "https://procedureradar.com/methodology"
    }
  ],
  "pagination": { "page": 1, "limit": 25, "total": 1, "pages": 1, "has_next": false, "has_previous": false },
  "meta": { "timestamp": "2026-10-14T15:30:00.000Z", "version": "1.0.0", "tier": "growth", "granularity_state": "full" }
}

SDKs and Libraries

Official SDKs are coming soon. In the meantime, any HTTP client works. The examples above cover Python, JavaScript, and cURL. The API is standard REST with JSON responses, so integration is straightforward in any language.Official SDKs coming soon. Any HTTP client works. The API is standard REST with JSON responses.

Python

Node.js

cURL

Ready to Integrate?

Real hospital pricing data in your product. Apply today, ship this week.Real hospital pricing in your product. Apply today, ship this week.

Apply for API Access Book a 30-Minute Call

Comparing plans? See API pricing. Want to see the data first? Download The Verified Data Sample.

About the Data. Pricing data available through the ProcedureRadar API comes from two kinds of federally mandated file: hospital Machine-Readable Files required under 45 CFR Part 180, and payer-published negotiated rate files required under the Transparency in Coverage rule, which are served at Scale and above with scope that varies by payer: some payer rates come from network-wide files, some from many employer groups' files, and one from a single large employer group's rate file, as GET /v1/payers lists for each insurer. ProcedureRadar processes these files monthly, normalizing billing codes to consumer-friendly procedure names and quality-scoring every record. Actual costs may vary based on insurance plan, diagnosis, and treatment complexity. This data is for informational and comparison purposes only. ProcedureRadar does not provide medical advice. Read our methodology.

API documentation reflects the current production specification.

Documentation reviewed: October 4, 2026