Pay-per-call EHR data endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at `/api/v1/ehr/70` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs accessible via the x402 payment protocol on the Base network. The specific endpoint appears to serve Electronic Health Record (EHR) data, though the crawled documentation provides no details about the schema, fields, or data source behind this particular route. The platform advertises a uniform $0.02 per request pricing model with no API keys, no rate limits, and instant access.
Payment is settled in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The x402 challenge confirms the endpoint is live, accepting POST requests with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The payment recipient address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the timeout is 300 seconds.
The platform lists many other endpoints across categories like AI/ML, finance, infrastructure, and data analytics, all at the same $0.02 price point. However, the `/api/v1/ehr/70` endpoint is not listed on the homepage catalog, and no documentation was found describing its request format, expected input body, or response schema. The "EHR" naming suggests electronic health records, but without documentation this is speculative. Prospective users should test the endpoint carefully and be aware that health data APIs may be subject to regulatory requirements (e.g., HIPAA).
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request basis
- —Integrating EHR data into agent workflows without API key management
- —Programmatic access to health data with crypto micropayments
Fit
Best for
- —Developers needing on-demand EHR data access without subscriptions
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping health data integrations with low per-call cost
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation and guaranteed SLAs before integrating
- —Non-crypto users who cannot settle payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/70 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is zero documentation on what this EHR endpoint accepts or returns — no request schema, no response schema, no examples. The endpoint isn't even listed in the provider's own homepage catalog. This is effectively a stub listing.
Warnings
- —No documentation found for /api/v1/ehr/70 — request/response schema is completely unknown.
- —The endpoint is not listed on the provider's homepage API catalog, raising questions about its status.
- —EHR (Electronic Health Records) data may be subject to HIPAA or other health data regulations — compliance status is unknown.
- —All non-homepage crawled pages returned only 'Connect wallet' with no useful content, suggesting docs are behind a wallet gate or not yet built.
Citations
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC (6 decimals) = $0.02, with a 300-second timeout.https://lowpaymentfee.com/api/v1/ehr/70
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/ehr/70