Pay-per-call medical records API 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/42`) 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 — 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 on the Base network. This specific endpoint falls under a "medical records" path, but the crawled site does not list it among its publicly advertised APIs, nor does it provide documentation on the request body schema or the structure of the returned medical record data. The endpoint is live and responds with a well-formed x402 challenge (HTTP 402), confirming it is operational.
Because no OpenAPI spec, request/response examples, or detailed documentation were found for this particular endpoint, the exact fields accepted in the POST body and the shape of the response remain unknown. Callers should treat this as an exploratory endpoint and be aware that it appears to serve health-related data, which may carry regulatory implications (e.g., HIPAA in the US).
Capabilities
Use cases
- —Retrieving medical record data for a specific record ID via a single paid API call
- —Integrating health data into agent workflows without managing API keys or subscriptions
- —Programmatic access to medical records with instant crypto-settled micropayments
Fit
Best for
- —Developers or agents needing on-demand medical record lookups without subscription overhead
- —x402-compatible agents that can settle USDC payments on Base
- —Prototyping health data integrations with minimal setup
Not for
- —Production healthcare systems requiring HIPAA-compliant audit trails and BAAs
- —Bulk retrieval of large medical datasets (pay-per-call model may be costly at scale)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/42 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation for this specific medical records path, and it is not listed among the provider's publicly advertised APIs. The medical/health data category raises regulatory concerns with no compliance information available.
Warnings
- —No documentation or schema found for /api/v1/medical/records/42 — request body and response format are unknown.
- —This endpoint is not listed among the provider's publicly advertised APIs; it may be a demo, test, or unlisted resource.
- —Endpoint serves health/medical data — potential regulatory implications (HIPAA, GDPR health data provisions) with no compliance information provided.
- —The record ID '42' is hardcoded in the path; it is unclear whether other record IDs are accessible or how discovery works.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, requiring USDC payment on Base network with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/medical/records/42
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/42
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The medical records endpoint is not listed among the provider's publicly advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure).https://lowpaymentfee.com