x402-gated EHR endpoint on Base, pay $0.02 per request in USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/14` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific resource at path `/ehr/14` is labeled "Premium API Access" but its exact functionality is unclear — the "ehr" path segment suggests Electronic Health Records, though no documentation confirms what data or service this endpoint actually returns.
The endpoint is live and responds with a valid x402 payment challenge. It accepts POST requests and settles on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum amount required is 20,000 base units of USDC, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing across all endpoints. Payment is made via the `exact` scheme with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.
Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the `/ehr/14` endpoint accepts as input or returns as output. The platform lists many endpoint categories but `/api/v1/ehr/14` does not appear on the homepage's catalog, making it an unlisted or legacy route. Users should exercise caution given the lack of documentation and the potentially sensitive nature of EHR data.
Capabilities
Use cases
- —Retrieving electronic health record data (if confirmed) via a single pay-per-call request
- —Integrating health data into agent workflows without managing API keys
- —Programmatic access to structured medical records on a per-request payment basis
Fit
Best for
- —Developers needing key-free, pay-per-call access to health data endpoints
- —AI agents that can settle x402 payments on Base in USDC
- —Prototyping integrations where low per-request cost matters
Not for
- —Production healthcare applications requiring documented, HIPAA-compliant APIs
- —Users who need detailed schema documentation or guaranteed SLAs
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/14 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the /ehr/14 resource actually does, what inputs it expects, or what it returns. No OpenAPI schema, no examples, and the endpoint isn't even listed on the provider's homepage catalog. The potentially sensitive healthcare data domain with no compliance information further lowers confidence.
Warnings
- —The /api/v1/ehr/14 path is not listed on the provider's homepage catalog — it may be unlisted, experimental, or deprecated.
- —'EHR' typically refers to Electronic Health Records, a regulated data category. No HIPAA compliance, data provenance, or privacy documentation is provided.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no substantive content.
- —No request or response schema is available — callers cannot know what to send or what to expect back.
- —The endpoint's actual functionality is unverified; 'Premium API Access' is a generic label.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/14
- —The platform advertises $0.02/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/ehr/14
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs