Hpsa Search
by api.healthparse.io in Search & web
Find HRSA Health Professional Shortage Areas (Primary Care / Dental / Mental Health) by state, discipline, minimum shortage score, or FTE shortage — a mapped staffing-demand signal. Answers: where is the designated shortage most severe, and how many practitioner FTEs are needed? Powers medical & travel-nurse staffing. Defaults to currently-designated areas. Filter: state, discipline, min_score, min_fte, rural_status, designated_since, status; sort by hpsa_score or hpsa_fte.
https://api.healthparse.io/v1/hpsa/search- Price
- $0.03
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 250 ms
- 372 ms slowest 5%
- Last check
- Passed
- 44 min ago, next any minute now
Reliability
How to call it
GET https://api.healthparse.io/v1/hpsa/search
Each call costs $0.03 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/hpsa/search?discipline=example&min_score=example&state=exampleExample response
The provider's example. We can't check it without paying.
{
"records_notice": "Observational roster of HRSA Health Professional Shortage Area designations. One row per HPSA component (facility/geography) per discipline; a higher hpsa_score (0-26) and larger hpsa_fte shortage indicate greater designated shortage — a staffing-demand signal, not a judgment about any provider.",
"rows": [
{
"county_name": "Duval",
"designation_date": "2018-06-01",
"discipline_class": "Primary Care",
"hpsa_fte": 12.5,
"hpsa_id": "1123456789",
"hpsa_name": "Low Income - Duval County",
"hpsa_score": 18,
"primary_state": "FL",
"status": "Designated"
}
],
"total_matched": 1
}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.03.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.healthparse.io/v1/hpsa/search?discipline=example&min_score=example&state=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/hpsa/search?discipline=example&min_score=example&state=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.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
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.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.healthparse.io%2Fv1%2Fhpsa%2Fsearch
const res = await pay("https://api.healthparse.io/v1/hpsa/search?discipline=example&min_score=example&state=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.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
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/hpsa/search?discipline=example&min_score=example&state=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 |
|---|---|---|---|---|
| 44 min ago | Passed | 402 | 214 ms | $0.03 |
| 5 h ago | Passed | 402 | 231 ms | $0.03 |
| 9 h ago | Passed | 402 | 207 ms | $0.03 |
| 13 h ago | Passed | 402 | 250 ms | $0.03 |
| 17 h ago | Passed | 402 | 233 ms | $0.03 |
Show 10 older checks
| 21 h ago | Passed | 402 | 274 ms | $0.03 |
| 25 h ago | Passed | 402 | 254 ms | $0.03 |
| 28 h ago | Passed | 402 | 253 ms | $0.03 |
| 32 h ago | Passed | 402 | 286 ms | $0.03 |
| 36 h ago | Passed | 402 | 255 ms | $0.03 |
| 39 h ago | Passed | 402 | 363 ms | $0.03 |
| 43 h ago | Passed | 402 | 932 ms | $0.03 |
| 46 h ago | Passed | 402 | 180 ms | $0.03 |
| 2 days ago | Passed | 402 | 320 ms | $0.03 |
| 2 days ago | Passed | 402 | 185 ms | $0.03 |