Developers

Pay-per-call API over the Healthparse dataset family: hospital cost-report financials, price-transparency negotiated rates, sanctions screening, nonprofit Form 990 filings, Medicare provider analytics, wage benchmarks, CMS quality ratings, and provider change-event feeds. Every response carries a signed attestation (_meta.signature) and per-dataset license terms.

Base URL: https://api.healthparse.io · Machine-readable catalog · license terms · MCP server at https://api.healthparse.io/mcp (streamable HTTP, x-api-key auth; every endpoint below is a tool).

Two ways to pay

1. API key — metered billing via Stripe. Pass it in the x-api-key header (or as a Bearer token). Get an API key below.

curl -H "x-api-key: YOUR_KEY" \
  "https://api.healthparse.io/v1/hospitals/search?state=TX&limit=5"

2. x402 — no account, no key. Call any endpoint bare and the gateway answers 402 Payment Required with the exact USDC price on Base in the accepts array; an x402 client (e.g. x402-fetch) pays and retries automatically. Settlement is on-chain and gasless for the payer.

# Bare call returns the 402 challenge with pricing:
curl -i "https://api.healthparse.io/v1/hospitals/450054"

# An x402 client handles the payment round-trip for you:
#   import { privateKeyToAccount } from "viem/accounts";
#   import { wrapFetchWithPayment } from "x402-fetch";
#   const payFetch = wrapFetchWithPayment(fetch, privateKeyToAccount(PK));
#   await payFetch("https://api.healthparse.io/v1/hospitals/450054");

Get an API key

Keys bill per call at the prices in the table below — no flat fee, no monthly minimum. Subscribing (free to start, card on file) activates metered billing for your account; you then create a key and pass it as x-api-key.

Subscribe — pay per call →

After checkout you'll land on a welcome page to set your password. Once signed in, create and manage keys at healthparse.io/account (each key is shown once — save it), or via the API:

curl -X POST https://healthparse.io/api/platform/api-keys \
  -H "cookie: $HEALTHPARSE_SESSION_COOKIE" \
  -H "content-type: application/json" \
  -d '{"name": "my-agent"}'

How billing works

• Every endpoint has a fixed price per call — listed in the table below and in the machine-readable catalog. There is no flat fee, no monthly minimum, and no per-seat charge.
• Each successful call is metered as it happens. Your invoice is simply the sum of the per-call prices for the month. Failed calls (4xx/5xx) are not billed.
• One invoice per month from Stripe (Healthparse), charged to your card on file at the end of each billing cycle. Example: 1,000 hospital searches at $0.02 + 200 exclusion screens at $0.15 = $20.00 + $30.00 = $50.00.
• Under the hood, usage is reported to Stripe in millionths of a dollar so the month-end sum is exact to the cent — a $0.02 call meters as 20,000 units at $0.000001 each. You'll see this unit math on the invoice line item; the dollar total always equals the catalog prices you saw.
• Prefer no account at all? Every endpoint also accepts x402: call it bare, get an HTTP 402 challenge, settle in USDC on Base per call. Same prices, no subscription, no invoice.

Questions, invoicing, or higher rate limits: hello@healthparse.io.

Endpoints (42)

Webhooks

The provider change-event feed (providers.events.feed) can also push to you: a webhook subscription filters events by type and/or state and POSTs matching events to your HTTPS endpoint at the end of every refresh run, batched, in ascending event_id order. Subscriptions are set up per account (not self-serve yet) — email hello@healthparse.io with your gateway key, filters, and endpoint URL. See a full sample delivery.

• Signature — every request carries X-Healthparse-Signature: sha256=<hex>, an HMAC-SHA256 of the raw request body with your subscription secret, plus X-Healthparse-Delivery (per-delivery UUID) and X-Healthparse-Event-Count. Verify by recomputing the HMAC over the exact raw body before parsing.
• Delivery semantics — at-least-once. Each subscription keeps a strict cursor (last_delivered_event_id) that advances only after your endpoint returns 2xx; a failed or timed-out delivery is retried with the same events on the next refresh run. Dedupe on event_id or dedupe_key.
• Payload — JSON: { subscription_id, delivered_at, event_count, events: [...] }, where each event has the same shape as a /v1/providers/events row.

# Verify a delivery (Node):
const { createHmac, timingSafeEqual } = require("node:crypto");
const expected = "sha256=" +
  createHmac("sha256", SECRET).update(rawBody, "utf8").digest("hex");
const ok = timingSafeEqual(
  Buffer.from(expected), Buffer.from(req.headers["x-healthparse-signature"]));

Full input schemas and output examples for every endpoint are in the JSON catalog. Data is derived from public U.S. government sources; per-dataset attribution and redistribution terms are at /v1/license.