Yoy Increase Search
by api.healthparse.io in Search & web
Manufacturers/GPOs whose TOTAL Open Payments spend genuinely increased year-over-year — a real per-manufacturer delta (amount_current vs amount_prior), not a magnitude threshold. Defaults to 2023→2024 (any loaded year pair via year/prior_year). Filter: specialty, state, min_increase_usd (default $10,000), min_pct_change (default 10%). NOTE: op_manufacturer_payments holds only PY2024 today — real, returns total_matched=0 (never fabricated) until a prior year is imported; see stage1b-report.md.
GET https://api.healthparse.io/v1/manufacturers/yoy-increase/search
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 226 ms typical, 468 ms slowest 5%
- Last check
- 4 h ago
- Next check
- any minute now
How to call it
GET https://api.healthparse.io/v1/manufacturers/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/manufacturers/yoy-increase/search?prior_year=example&state=example&year=exampleExample response
The provider's example. We can't check it without paying.
{
"prior_year": 2023,
"records_notice": "Observational year-over-year rollup of the CMS Open Payments (Sunshine Act) General Payments file, keyed on the paying manufacturer/GPO (op_manufacturer_payments, entity-resolved). amount_current/amount_prior are the company's TOTAL reported payments in the current vs prior program year; delta and pct_change are computed from those two real totals. Only manufacturers reporting payments in BOTH years, with a real increase, are returned. Not a judgment about the company or its products.",
"rows": [],
"selectors": [
"year=2024",
"prior_year=2023",
"min_increase_usd=10000",
"min_pct_change=10"
],
"total_matched": 0,
"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/manufacturers/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/manufacturers/yoy-increase/search?prior_year=example&state=example&year=example' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fmanufacturers%2Fyoy-increase%2Fsearch
const res = await pay("https://api.healthparse.io/v1/manufacturers/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/manufacturers/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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 269 ms | $0.1 |
| 8 h ago | Passed | 402 | 259 ms | $0.1 |
| 11 h ago | Passed | 402 | 249 ms | $0.1 |
| 15 h ago | Passed | 402 | 393 ms | $0.1 |
| 19 h ago | Passed | 402 | 234 ms | $0.1 |
| 23 h ago | Passed | 402 | 168 ms | $0.1 |
| 27 h ago | Passed | 402 | 171 ms | $0.1 |
| 31 h ago | Passed | 402 | 226 ms | $0.1 |
| 34 h ago | Passed | 402 | 178 ms | $0.1 |
| 38 h ago | Passed | 402 | 217 ms | $0.1 |
| 41 h ago | Passed | 402 | 186 ms | $0.1 |
| 45 h ago | Passed | 402 | 485 ms | $0.1 |
| 2 days ago | Passed | 402 | 224 ms | $0.1 |
| 2 days ago | Passed | 402 | 179 ms | $0.1 |
| 2 days ago | Passed | 402 | 468 ms | $0.1 |