Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402 endpoint at lowpaymentfee.com serves medical record data (record ID 62) behind a micropayment wall. It uses the x402 "exact" payment scheme on the Base network, accepting USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units — which equals $0.02 per request (USDC uses 6 decimals). The endpoint accepts POST requests and returns application/json.
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 uniformly priced at $0.02 per request. No API keys or rate limits are advertised; access is gated solely by the x402 payment header. The site settles payments on the Base L2 network.
Important caveat: this specific endpoint is labeled "medical/records/62" but no documentation, schema, or sample response is available. It is unclear what data is returned, whether it is real patient data (which would carry regulatory implications) or synthetic/demo data. The endpoint is confirmed live (402 challenge captured), but the lack of any request/response documentation makes it difficult to evaluate fitness for production use.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without API key management
- —Demonstrating x402 micropayment flows with a medical data endpoint
Fit
Best for
- —Agents needing on-demand medical record lookups with no subscription
- —Developers exploring x402 payment-gated API patterns
- —Applications requiring keyless, pay-as-you-go data access on Base
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees (no compliance documentation available)
- —Use cases needing bulk or batch medical data retrieval at scale
- —Applications that need detailed request/response schema documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/62 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is zero documentation on request parameters, response schema, or the nature of the medical data returned. The endpoint path suggests regulated health data but no compliance or data-source information is provided. Effectively a stub listing.
Warnings
- —No request or response schema documentation available — unknown what data is returned
- —Endpoint path suggests medical/health data; no HIPAA or regulatory compliance information is provided
- —No OpenAPI spec, no examples, no README content accessible (pages behind wallet connect)
- —It is unclear whether this returns real, synthetic, or placeholder medical data
Citations
- —Endpoint returns 402 with x402 challenge accepting USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/62
- —Provider advertises $0.02 per request, no API keys, no rate limits, Base network settlementhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/62