Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at `/api/v1/medical/records/27` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on the Base network with no API keys, no rate limits, and no subscriptions required.
The specific resource at `/api/v1/medical/records/27` is labeled "Premium API Access" and costs up to $0.02 per request (maxAmountRequired of 20,000 base units of USDC, which has 6 decimals = $0.02). It accepts POST requests and returns `application/json`. The x402 challenge was confirmed live, returning a standard 402 Payment Required response with a valid payment challenge.
Important caveats: the endpoint path suggests it serves medical records, which falls into a regulated data category. No documentation, OpenAPI schema, or example responses were found in the crawl. The actual data returned behind the paywall is unknown — it could be synthetic/demo data or real medical records. Prospective consumers should exercise caution and verify the nature of the data before integrating.
Capabilities
Use cases
- —Retrieving medical record data (record ID 27) on a per-call payment basis
- —Integrating pay-per-request health data into agent workflows without API key management
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers exploring x402 payment protocol with real endpoints
- —Agents needing on-demand data access without subscription commitments
- —Low-volume, pay-as-you-go API consumption on Base
Not for
- —Production healthcare applications requiring HIPAA-compliant, verified medical data sources
- —High-volume batch retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation or schema guarantees before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/27 \
-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 OpenAPI schema, no documentation, no example request/response, and the nature of the data behind the paywall is entirely unknown. The medical records path raises regulatory concerns with zero supporting documentation.
Warnings
- —Endpoint path suggests medical/health records — this is a regulated data category. No compliance information (HIPAA, etc.) is provided.
- —No OpenAPI spec, no documentation, and no example responses are available. The actual payload behind the paywall is unknown.
- —The specific record ID (27) is hardcoded in the path; it is unclear whether other record IDs exist or what data model is used.
- —The crawled /api, /pricing, and /README pages returned only 'Connect wallet' with no useful content.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/27
- —The platform advertises $0.02 per request pricing 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/27