Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This x402-enabled endpoint at lowpaymentfee.com serves medical record data at the path `/api/v1/medical/records/23`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint probed (`/api/v1/medical/records/23`) returned a valid 402 challenge with a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. Payment is made via the x402 "exact" scheme to the specified wallet address. The endpoint accepts POST requests and returns `application/json`. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation is extremely sparse. The landing page lists available API categories and a uniform $0.02 price, but provides no request/response schemas, parameter descriptions, or example payloads for any endpoint — including this medical records one. The nature of the data returned (whether it is synthetic/demo data or real medical records) is entirely unclear from the available material. Given the "medical/records" path, users should exercise caution regarding data authenticity, regulatory compliance (HIPAA, GDPR), and intended use.
Capabilities
Use cases
- —Retrieving medical record data via a single micropayment
- —Integrating pay-per-call health data into agent workflows
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents needing on-demand data access without API key provisioning
- —Prototyping pay-per-call data retrieval pipelines
Not for
- —Production healthcare applications requiring HIPAA-compliant, verified medical data
- —Use cases needing bulk data export or batch queries at scale
- —Applications requiring detailed API documentation or SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/23 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is zero documentation on request parameters, response schema, or the nature of the medical records data. No examples or OpenAPI spec are available. The medical records domain raises regulatory concerns that are unaddressed.
Warnings
- —No request or response schema documented for this endpoint
- —Nature of 'medical records' data is completely unknown — could be synthetic, demo, or real data
- —Medical/health data may be subject to HIPAA, GDPR, or other regulations; no compliance information provided
- —No documentation pages rendered useful content (all showed only 'Connect wallet')
- —The specific record ID '23' is hardcoded in the path; unclear if other IDs are available or how to discover them
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/23
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/23