x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/95` 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 endpoint appears to serve Electronic Health Record (EHR) data, though the crawled documentation provides no details about the `/ehr/` path — it is not listed among the publicly advertised API categories on the site's landing page. The endpoint is live and returns a valid x402 challenge.
Payment is settled on the Base network using USDC (contract `0x8335…2913`). The `maxAmountRequired` is 20,000 base units; since USDC uses 6 decimals, this equals $0.02 per request — consistent with the site's advertised flat $0.02/request pricing across all endpoints. The platform advertises no API keys, no rate limits, and instant access; callers pay via the x402 `X-PAYMENT` header.
Because the `/ehr/95` path is not documented on the site and no input/output schema beyond `POST application/json` is provided, the actual request body format and response structure are unknown. The "EHR" label and the numeric ID `95` suggest it may return a specific health record resource, but this is speculative. Prospective callers should be aware that no documentation, examples, or schema details are available for this particular route.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR lookups into agent workflows without managing API keys
- —Accessing health data via crypto micropayments on Base
Fit
Best for
- —Agents or apps needing on-demand EHR data without subscription commitments
- —Developers experimenting with x402 pay-per-call patterns
- —Workflows requiring keyless, instant-access health data endpoints
Not for
- —Production healthcare systems requiring HIPAA-compliant, documented APIs with SLAs
- —Use cases needing bulk or batch EHR data retrieval at scale
- —Users who need detailed schema documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/95 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but the /ehr/95 path is completely undocumented — it does not appear on the provider's landing page or any crawled page. No input schema, output schema, or example responses are available. The EHR label is inferred solely from the URL path.
Warnings
- —The /api/v1/ehr/95 endpoint is not listed in the provider's public API catalog — its existence and purpose are unverified beyond the URL path.
- —No request or response schema is documented; callers must discover the interface by experimentation.
- —EHR (Electronic Health Record) data may be subject to healthcare regulations (e.g., HIPAA); no compliance information is provided.
- —The docs, pricing, API, and README pages all returned only a 'Connect wallet' prompt with no substantive content.
Citations
- —The site advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/ehr/95
- —The /ehr/95 path does not appear among the publicly listed API endpoints on the landing page.https://lowpaymentfee.com