Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This x402-enabled endpoint at `/api/v1/medical/records/29` is part of the lowpaymentfee.com platform, which hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific endpoint probed here appears to serve medical record data (record ID 29). 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). The x402 challenge is live and responds with a version-1 402 payment challenge on POST.
The platform advertises a uniform $0.02-per-request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required. Authentication is handled entirely through the x402 payment header. The endpoint accepts POST requests and returns `application/json` responses. No detailed request/response schema or documentation beyond the landing page listing is available — the /api, /pricing, and /README pages all resolve to a minimal "Connect wallet" prompt.
Because this endpoint is labeled as serving medical records, consumers should exercise caution regarding the nature, provenance, and regulatory status of the data returned. No documentation clarifies whether the data is synthetic, anonymized, or subject to health-data regulations such as HIPAA. The lack of any OpenAPI spec, request schema, or sample responses makes it difficult to evaluate the endpoint's actual utility without making a paid call.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Integrating health data into agent workflows without API key management
- —Testing x402 micropayment flows against a live endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing on-demand data access without subscription commitments
- —Prototyping pay-per-call data retrieval pipelines
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling
- —Use cases needing detailed API documentation or guaranteed SLAs
- —Bulk data retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/29 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and the medical-records label raises regulatory concerns with zero clarification provided.
Warnings
- —No request or response schema available — actual data returned is unknown
- —Endpoint labeled 'medical records' with no documentation on data provenance, whether data is synthetic, or regulatory compliance (e.g., HIPAA)
- —No OpenAPI spec, no README content, and ancillary pages (/api, /pricing, /README) return only a wallet-connect prompt
- —This is a single-record endpoint (/records/29); unclear if other record IDs are available or what they represent
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/29
- —Platform-wide pricing is $0.02 per request with no API keys, no rate limits, and no minimumshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/29