HIPAA health records endpoint paid per-request via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to HIPAA-related health records via a pay-per-call x402 protocol. The specific resource `/api/v1/hipaa/records/28` is accessed via HTTP POST and costs $0.02 per request, settled in USDC on the Base network. No API keys or rate limits are required — callers simply attach an x402 payment header with each request.
The broader lowpaymentfee.com platform hosts a variety of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, this specific listing is for the HIPAA records endpoint. The x402 challenge confirms the endpoint is live, accepting payments to address `0x1A2B...85F3` in USDC (`0x8335...2913`) on Base.
Important caveats: The endpoint's actual response schema is undocumented — no OpenAPI spec, no example responses, and the crawled docs/pricing/README pages all returned only a "Connect wallet" stub with no meaningful content. The HIPAA label raises regulatory concerns: serving protected health information via a permissionless pay-per-call API with no authentication beyond payment would be unusual for a compliant HIPAA-covered entity. Callers should exercise caution and verify the nature of the data returned before relying on this endpoint for any health-data workflow.
Capabilities
Use cases
- —Retrieving health record data for record ID 28 via a single paid request
- —Integrating HIPAA record lookups into agent workflows that settle payments on Base
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers exploring x402 payment protocol integrations
- —Agents needing on-demand health record access without API key provisioning
- —Prototyping pay-per-call data retrieval pipelines
Not for
- —Production HIPAA-compliant healthcare workflows (compliance status unverified)
- —Bulk data retrieval or batch processing (per-request pricing, no documented batch mode)
- —Users who need detailed response schema documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/28 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/hipaa/records/28",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402_payment_token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no response schema, no example responses, and the docs pages are empty stubs. The HIPAA label raises significant regulatory red flags with no evidence of compliance documentation.
Warnings
- —HIPAA-labeled endpoint with no visible compliance documentation or authentication beyond payment — regulatory risk
- —No OpenAPI spec or response schema available; actual response format is unknown
- —All documentation pages (/docs, /pricing, /README, /api) returned only 'Connect wallet' with no content
- —This endpoint serves a single record ID (28); unclear if other record IDs are available or what data is returned
Citations
- —Endpoint returns 402 with x402 challenge accepting USDC on Base networkhttps://lowpaymentfee.com/api/v1/hipaa/records/28
- —Platform pricing is $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/hipaa/records/28
- —maxAmountRequired is 20000 base units (USDC 6 decimals = $0.02)https://lowpaymentfee.com/api/v1/hipaa/records/28