HIPAA health records endpoint payable per-request via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to a HIPAA-related health record (record ID 94) via the x402 payment protocol. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals). No API keys or rate limits are advertised; callers pay per request by attaching an X-PAYMENT header.
The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities—all priced at $0.02 per request on the Base network. However, the specific endpoint listed here is under the path `/api/v1/hipaa/records/94`, which is not featured on the site's public landing page. No documentation, request schema, or response schema is provided for this particular endpoint beyond the x402 challenge metadata. The HIPAA label suggests it may return protected health information, but no details on data format, required POST body, or compliance guarantees are available from the crawled material.
Because the endpoint is live (returns a valid 402 challenge) but lacks any documentation, example payloads, or explanation of what the returned record contains, consumers should treat this as an opaque, undocumented endpoint. The HIPAA label raises regulatory concerns that are not addressed in any visible documentation.
Capabilities
Use cases
- —Retrieving a specific HIPAA health record on demand with per-call payment
- —Integrating health data into agent workflows without subscription overhead
- —Programmatic access to medical record data settled via crypto micropayment
Fit
Best for
- —Agents or applications needing on-demand health record access with no API key
- —Developers experimenting with x402 pay-per-call protocols on Base
- —Scenarios where per-request billing is preferred over subscriptions
Not for
- —Production healthcare applications requiring documented compliance guarantees
- —Use cases needing bulk or batch health record retrieval
- —Callers who cannot settle payments in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/94 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schemas, no examples, and the HIPAA label raises serious regulatory questions with no visible compliance information. The endpoint path is not listed on the site's own landing page. Effectively a stub listing.
Warnings
- —No documentation or schema available for this specific endpoint
- —HIPAA-labeled endpoint with no visible compliance, privacy policy, or BAA documentation
- —Endpoint path /api/v1/hipaa/records/94 is not listed on the provider's public landing page
- —No request body schema or response schema provided—callers cannot know what to send or expect
- —Regulated health data category: verify legal and compliance requirements before use
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired 20000https://lowpaymentfee.com/api/v1/hipaa/records/94
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/hipaa/records/94
- —The site advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The landing page lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories but does not list the /api/v1/hipaa/records pathhttps://lowpaymentfee.com