Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/88`) 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 amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required; access is granted immediately upon payment.
The provider, lowpaymentfee.com, hosts a broader 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. The specific endpoint listed here targets medical records, though the crawled material does not document the request body schema, response fields, or the nature of the medical data returned. The x402 challenge was successfully captured (HTTP 402 with valid accepts block), confirming the endpoint is live.
Because the endpoint deals with medical records, consumers should be aware of potential regulatory implications (e.g., HIPAA in the US, GDPR in the EU). No documentation was found describing data provenance, compliance certifications, or the structure of the returned records. The lack of an OpenAPI spec, request/response examples, or any substantive documentation beyond the landing page limits confidence in what this endpoint actually returns.
Capabilities
Use cases
- —Retrieving medical record data for record ID 88 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-gated health data APIs
- —Use cases where keyless, per-call billing 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/88 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request/response schema, no OpenAPI spec, and the medical records domain raises regulatory concerns with no compliance information provided. Effectively a stub listing.
Warnings
- —No request or response schema documented — unknown what data is returned
- —Medical/health data category may be subject to HIPAA, GDPR, or other regulations; no compliance information found
- —No OpenAPI spec, no examples, no README content available
- —The specific record ID '88' is hardcoded in the URL; unclear if other IDs are supported or how to discover them
- —Provider landing page lists this endpoint category but does not specifically list /medical/records paths
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/medical/records/88
- —Payment is 20,000 base units of USDC (USD Coin, 6 decimals = $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/88
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/88