Pay-per-call medical records endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/37` 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. The specific endpoint probed appears to serve medical record data (record ID 37) behind a micropayment wall. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.
The x402 challenge indicates a maximum amount of 20,000 base units of USDC. Since USDC uses 6 decimals, this converts to $0.02 per request — consistent with the site-wide $0.02/request pricing advertised on the landing page. The endpoint accepts POST requests, returns `application/json`, and requires no API keys or rate limits according to the provider's documentation. Timeout for payment settlement is 300 seconds.
Important caveat: the endpoint is labeled as serving "medical records," which falls into a regulated data category. No documentation exists describing the actual data schema, what the records contain, or whether they are synthetic/demo data versus real patient information. The provider's landing page does not specifically list this medical records endpoint among its advertised APIs, and no OpenAPI spec or detailed docs were found. Treat this endpoint with caution given the sensitive nature of medical data.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Integrating health data into agent workflows without subscription commitments
- —Demonstrating x402 micropayment flows for data access
Fit
Best for
- —Agents needing on-demand medical record lookups with no subscription
- —Developers exploring x402 payment protocol integrations
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data sources
- —High-volume bulk medical data ingestion (no documented batch endpoints)
- —Use cases requiring detailed schema documentation or SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/37 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no response schema, no documentation for this specific medical records endpoint, and the landing page doesn't even list it among advertised APIs. The medical/health data category raises regulatory concerns with zero transparency about data provenance.
Warnings
- —Medical/health data category — no documentation on data provenance, compliance (HIPAA), or whether records are synthetic vs. real
- —This specific endpoint (/api/v1/medical/records/37) is not listed among the provider's advertised APIs on the landing page
- —No OpenAPI spec, response schema, or example responses available
- —No robots.txt or agents.txt found; /api, /pricing, and /README pages returned only 'Connect wallet' with no useful content
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/37
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/37