HIPAA health records endpoint, pay-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/96` is described generically as "Premium API Access" and accepts POST requests. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced uniformly at $0.02 per call. However, the specific HIPAA records endpoint is not listed on the provider's public landing page among the advertised API categories, and no documentation, request/response schema, or example payloads are available for it. The crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.
Because this endpoint deals with HIPAA-regulated health data, consumers should exercise caution. There is no published documentation explaining what data is returned, what input the POST body expects, or how PHI (Protected Health Information) compliance is maintained. The endpoint is live (returns a valid 402 challenge), but the lack of transparency around the data model and compliance posture is a significant concern.
Capabilities
Use cases
- —Retrieving specific HIPAA health records programmatically
- —Integrating health data into agent workflows with per-call payment
- —Accessing medical record data without subscription or API key management
Fit
Best for
- —Agents needing on-demand access to health record data
- —Developers prototyping healthcare integrations with minimal setup
- —Pay-as-you-go access to regulated health data
Not for
- —Production healthcare applications requiring documented compliance guarantees
- —Use cases needing detailed API documentation and schema validation
- —Bulk retrieval of large health record datasets
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/96 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no request/response schema, no examples, and the HIPAA records endpoint is not even listed on the provider's own landing page. The regulated health-data category amplifies the concern around missing compliance and schema information.
Warnings
- —HIPAA-regulated health data: no compliance documentation or privacy policy found
- —Endpoint /api/v1/hipaa/records/96 is not listed among the provider's publicly advertised APIs
- —No request body schema or response schema available — callers cannot know what to send or expect
- —All docs/pricing/README pages returned only 'Connect wallet' with no substantive content
- —No OpenAPI spec, ai-plugin manifest, or agents.txt found
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base network, maxAmountRequired 20000https://lowpaymentfee.com/api/v1/hipaa/records/96
- —Provider advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/hipaa/records/96
- —HIPAA records endpoint is not listed among the provider's publicly advertised API categorieshttps://lowpaymentfee.com