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 40) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an x402 payment header to each request.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per request. The specific endpoint `/api/v1/medical/records/40` is not listed on the provider's landing page among the advertised API categories, which raises questions about its documentation, intended use, and the nature of the data it returns. No OpenAPI schema, request/response examples, or detailed documentation were found for this endpoint.
The x402 challenge was successfully captured (HTTP 402 with a valid accepts block), confirming the endpoint is live. The payment scheme is "exact" with a max timeout of 300 seconds. The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, and funds are sent to 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.
Capabilities
Use cases
- —Retrieving medical record data for record ID 40 via a single paid API call
- —Integrating pay-per-use health data access into agent workflows
- —Demonstrating x402 micropayment protocol usage for data retrieval
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand medical record access without API key management
- —Micropayment-based data retrieval on Base network
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees (no compliance documentation found)
- —Bulk medical data retrieval (single-record endpoint, $0.02 per call)
- —Users who need detailed API documentation or schema definitions before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/40 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (valid 402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation for this specific medical records endpoint, and it is not listed among the provider's advertised APIs. The medical/health data category raises regulatory concerns with zero compliance documentation.
Warnings
- —This endpoint serves medical/health data but no HIPAA compliance, privacy policy, or data handling documentation was found.
- —The /api/v1/medical/records/40 path is not listed on the provider's landing page among advertised APIs — its provenance and data contents are unclear.
- —No request body schema or response schema is documented; callers must discover behavior empirically.
- —No OpenAPI spec, README, or detailed docs were accessible (pages returned only 'Connect wallet').
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/medical/records/40
- —Payment is 20,000 base units of USDC (6 decimals = $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/40
- —Platform advertises $0.02/request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/40