Pay-per-call EHR API endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at `/api/v1/ehr/40` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs accessible via the x402 payment protocol on the Base network. Payment is made in USDC (USD Coin) with no API keys, no rate limits, and no subscriptions required — each call costs $0.02 (20,000 base units of USDC with 6 decimals). The x402 challenge is live and returns a standard 402 response with payment details.
The specific endpoint `/api/v1/ehr/40` is labeled "Premium API Access" but the path strongly suggests it relates to Electronic Health Records (EHR). However, no documentation, schema, or example responses are available for this endpoint — the docs, pricing, and README pages all resolve to a minimal "Connect wallet" prompt with no further detail. The broader lowpaymentfee.com site lists categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities, but this particular EHR endpoint is not listed among them.
Without request/response schemas or documentation, the exact data returned by this endpoint is unknown. Callers should be aware that the EHR path may involve health-related data, which could carry regulatory implications (e.g., HIPAA). The endpoint accepts POST requests and returns `application/json`.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request basis
- —Integrating EHR data into agent workflows without subscription overhead
- —Accessing health-related data with crypto micropayments
Fit
Best for
- —Developers needing on-demand EHR data access without API key management
- —Agent-based systems that can settle payments via x402 on Base
- —Low-volume or sporadic health data lookups where subscriptions are wasteful
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —High-volume bulk EHR data retrieval where per-request pricing is inefficient
- —Users who need detailed documentation or guaranteed SLAs before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/40 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no request/response schema, no examples, and the endpoint is not even listed on the provider's own homepage. The EHR designation is inferred solely from the URL path. This is effectively a stub listing.
Warnings
- —No documentation or schema available for this endpoint — functionality is entirely unknown beyond the URL path hint
- —EHR (Electronic Health Records) data may be subject to healthcare regulations such as HIPAA; compliance status is unknown
- —This endpoint is not listed among the provider's advertised APIs on the homepage
- —Docs, pricing, and README pages all return only a 'Connect wallet' prompt with no useful content
Citations
- —The endpoint returns a live x402 402 challenge with USDC on Base network, maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/ehr/40
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base uses 6 decimals, so 20000 base units = $0.02https://lowpaymentfee.com