Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 65) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units 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-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request. This specific endpoint falls under a "medical/records" path, but no documentation exists describing the request body schema, the fields returned, or the nature of the medical data. The existing description is simply "Premium API Access," which is generic and uninformative.
Because the endpoint deals with medical records, consumers should exercise caution regarding data provenance, HIPAA compliance, and applicable regulations. No privacy policy, terms of service, or compliance documentation was found in the crawled material. The endpoint is live (returns a proper 402 challenge), but the lack of any schema, example payloads, or documentation significantly limits confidence in what it actually returns.
Capabilities
Use cases
- —Retrieving medical record data for record ID 65 via a single paid API call
- —Integrating pay-per-use medical data access into agent workflows
- —Programmatic access to health records without subscription or API key management
Fit
Best for
- —Agents needing on-demand medical record lookups with crypto micropayments
- —Developers exploring x402 payment protocol integrations
- —Use cases where keyless, pay-per-call access is preferred over subscriptions
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of large medical datasets (single-record endpoint, $0.02 each)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/65 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is zero documentation on request/response schemas, no examples, no OpenAPI spec, and the endpoint path (medical/records) suggests regulated health data with no compliance information available. The listing is essentially a stub.
Warnings
- —No request or response schema documented — unknown what data is returned
- —Endpoint serves medical records with no visible HIPAA compliance, privacy policy, or terms of service
- —The specific record ID (65) is hardcoded in the path; unclear if other IDs are available or what they represent
- —All crawled subpages (/api, /pricing, /README) returned only a 'Connect wallet' prompt with no useful content
- —Regulated category: medical/health data — consumers should verify legal compliance before use
Citations
- —Endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network at maxAmountRequired 20000https://lowpaymentfee.com/api/v1/medical/records/65
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/65
- —Provider advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com