Pay-per-call medical records API on Base, settled in USDC via x402.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 46) via the x402 payment protocol. Each request is a POST that costs $0.02 in USDC on the Base network, with no API keys, rate limits, or subscriptions required — payment is made inline with each HTTP call.
The endpoint is live and returns a standard x402 challenge (HTTP 402) advertising an "exact" payment scheme. The asset is USDC (contract 0x8335…2913 on Base) with a maxAmountRequired of 20000 base units, which equals $0.02 (USDC uses 6 decimals). The payment timeout is 300 seconds. The response MIME type is application/json.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utilities — all at the same $0.02/request price point. However, there is no public documentation describing the request body schema or the response payload for this specific medical records endpoint. The endpoint path suggests it returns structured medical record data for a specific record ID, but the exact fields and format are unknown. Given the "medical" label, consumers should be aware this may involve health-related data subject to regulatory considerations.
Capabilities
Use cases
- —Retrieving structured medical record data on a per-call basis without subscription
- —Integrating health record lookups into agent workflows with inline crypto payment
- —Accessing medical data programmatically where traditional API key provisioning is not desired
Fit
Best for
- —Agents or applications needing on-demand medical record access with no signup
- —Developers experimenting with x402 pay-per-call patterns on Base
- —Workflows requiring low-friction, low-cost data retrieval settled in USDC
Not for
- —Production healthcare systems requiring HIPAA-compliant data pipelines with audit trails
- —Bulk medical data retrieval where per-call pricing would be cost-prohibitive
- —Use cases requiring detailed API documentation and guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/46 \
-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 no documentation for request/response schemas, no OpenAPI spec, and no examples. The medical records domain raises regulatory concerns that are unaddressed. Effectively a stub listing.
Warnings
- —No request body schema or response schema documented — consumers cannot know what to send or what they will receive.
- —Endpoint serves medical/health data — may be subject to HIPAA or other health data regulations; no compliance information is provided.
- —No OpenAPI spec, README, or detailed docs available from the provider site.
- —The specific record ID (46) in the path is hardcoded; unclear if other record IDs are available or how discovery works.
Citations
- —The endpoint returns HTTP 402 with x402 challenge advertising USDC on Base at maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/46
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/46