Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves medical record data (record ID 66) behind a micropayment wall. It uses the x402 "exact" payment scheme on the Base network, accepting USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units — which, at 6 decimals for USDC, equals $0.02 per request. No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.
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 probed here (/api/v1/medical/records/66) is not listed on the site's public catalog, suggesting it may be a less-advertised or specialized route. The endpoint accepts POST requests and returns application/json.
Because the endpoint deals with medical records, consumers should exercise caution regarding data provenance, accuracy, and regulatory compliance (e.g., HIPAA in the US). No documentation, OpenAPI schema, or example responses were found for this specific endpoint, so the exact shape of the returned data is unknown. The platform's landing page confirms the pricing model and x402 integration but provides no further technical detail about request/response formats for this route.
Capabilities
Use cases
- —Retrieving medical record data for record ID 66 via a single micropayment
- —Integrating pay-per-call health data into agent workflows without API key management
- —Demonstrating x402 micropayment flows for data access on Base
Fit
Best for
- —Agents or apps needing on-demand medical record lookups with no subscription
- —Developers experimenting with x402 payment-gated data endpoints
- —Scenarios where per-request billing is preferred over monthly plans
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of many medical records (no batch endpoint documented)
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/66 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live (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 route, and the medical records domain raises regulatory concerns. The endpoint isn't even listed on the provider's own catalog page.
Warnings
- —No API documentation or OpenAPI schema available for this endpoint
- —Medical/health data category — consumers must assess regulatory compliance (HIPAA, GDPR, etc.)
- —This specific endpoint (/api/v1/medical/records/66) is not listed on the provider's public catalog
- —No example request or response payloads available; data format is unknown
- —Data provenance and accuracy of medical records is unverified
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/medical/records/66
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/66