Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 41) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
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 with no API keys, no rate limits, and no commitments. This specific endpoint falls under a "medical/records" path, though no documentation beyond the x402 challenge and the landing page listing exists. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data returned after payment is unknown.
Because this endpoint deals with medical records, consumers should exercise caution regarding data provenance, accuracy, and regulatory compliance (e.g., HIPAA in the US). The lack of documentation makes it impossible to verify what data is returned or its source.
Capabilities
Use cases
- —Retrieving medical record data for record ID 41 via a single paid API call
- —Integrating pay-per-call medical data into agent workflows without API key management
- —Programmatic access to health records settled in USDC on Base
Fit
Best for
- —Agents needing on-demand medical record lookups with crypto micropayments
- —Developers exploring x402 protocol integrations
- —Use cases where keyless, pay-per-request access is preferred
Not for
- —Production healthcare applications requiring HIPAA-compliant, auditable data pipelines
- —Bulk retrieval of large medical datasets (single-record endpoint, no batch support documented)
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/41 \
-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 parameters, response schema, or data content. The medical records domain raises regulatory concerns. No OpenAPI spec, no examples, and crawled pages beyond the landing are empty.
Warnings
- —Medical/health data endpoint with no documentation on data source, accuracy, or regulatory compliance (e.g., HIPAA).
- —No OpenAPI spec or request/response schema available — consumers cannot know what to send or what they will receive.
- —Only a single record ID (41) is referenced; unclear if other record IDs are supported or what they represent.
- —Provider site pages (/api, /pricing, /README) returned no useful content beyond 'Connect wallet'.
Citations
- —Endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/41
- —All APIs on lowpaymentfee.com are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/41