78trust / 100

Yoy Increase Search

by api.healthparse.io in Search & web

x402 APIPassing, checked 2 h ago

Physicians whose TOTAL CMS Open Payments industry payments genuinely increased year-over-year — a real per-NPI delta (amount_current vs amount_prior), not a magnitude threshold. Defaults to 2023→2024 (any loaded year pair selectable via year/prior_year). Filter: specialty, state, min_increase_usd (default $1,000), min_pct_change (default 10%). Only physicians paid in BOTH years with a real rise clearing both thresholds are returned. Public CMS provider-level data; not a consumer report.

GET https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
252 ms typical, 340 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

GET https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search

Each call costs $0.1 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search?prior_year=example&state=example&year=example

Example response

The provider's example. We can't check it without paying.

Example response, 28 lines
{
  "prior_year": 2023,
  "records_notice": "Observational year-over-year rollup of the CMS Open Payments (Sunshine Act) General Payments file, keyed on the recipient NPI. amount_current/amount_prior are the physician's TOTAL reported industry payments (all nature_of_payment categories summed) in the current vs prior program year; delta and pct_change are computed from those two real totals — not a single-period magnitude threshold. Only physicians who received a reported payment in BOTH years, with a real increase, are returned. A rise in reported payments is not a judgment about the physician or their prescribing — provider-level program data, not a consumer report, and not for FCRA-regulated eligibility decisions.",
  "rows": [
    {
      "amount_current": 203423.89,
      "amount_prior": 862.08,
      "delta": 202561.81,
      "npi": "1134115397",
      "pct_change": 23496.9,
      "prescriber_city": "Houston",
      "prescriber_name": "Doe, Jane",
      "prescriber_specialty": "Cardiology",
      "prescriber_state": "TX"
    }
  ],
  "selectors": [
    "year=2024",
    "prior_year=2023",
    "min_increase_usd=1000",
    "min_pct_change=10",
    "state=TX",
    "specialty=Cardiology"
  ],
  "total_matched": 873,
  "total_matched_capped": false,
  "year": 2024
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search?prior_year=example&state=example&year=example'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search?prior_year=example&state=example&year=example' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.healthparse.io%2Fv1%2Fopen-payments%2Frecipients%2Fyoy-increase%2Fsearch
const res = await pay("https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search?prior_year=example&state=example&year=example");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.healthparse.io/v1/open-payments/recipients/yoy-increase/search?prior_year=example&state=example&year=example")
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402168 ms$0.1
6 h agoPassed402258 ms$0.1
10 h agoPassed402255 ms$0.1
14 h agoPassed402254 ms$0.1
18 h agoPassed402252 ms$0.1
21 h agoPassed402340 ms$0.1
25 h agoPassed402174 ms$0.1
29 h agoPassed402350 ms$0.1
32 h agoPassed402322 ms$0.1
36 h agoPassed402234 ms$0.1
39 h agoPassed402259 ms$0.1
43 h agoPassed402234 ms$0.1
46 h agoPassed402248 ms$0.1
2 days agoPassed402292 ms$0.1
2 days agoPassed402252 ms$0.1