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/86` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific `/ehr/86` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document EHR endpoints among its advertised categories. The endpoint is live and returns a valid x402 challenge.
Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 "exact" scheme. The `maxAmountRequired` is 20,000 base units, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing. The endpoint accepts HTTP POST, requires no API keys or accounts, and advertises no rate limits. The x402 payment header is the sole authentication mechanism.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data the `/ehr/86` resource actually returns. The "86" in the path may be a record identifier, but this is speculative. Users should be aware that this endpoint deals with a category label ("EHR") that typically involves sensitive health data, and no privacy or compliance information is provided by the platform.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 86)
- —Integrating EHR data into agent workflows with per-request micropayments
- —Accessing health data without managing API keys or subscriptions
Fit
Best for
- —Agents needing on-demand EHR data access via x402 micropayments
- —Developers prototyping health-data integrations without signup friction
- —Scenarios where pay-per-use pricing is preferred over subscriptions
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Use cases needing detailed API documentation or guaranteed SLAs
- —Bulk retrieval of large EHR datasets (pay-per-request at $0.02 adds up)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/86 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the EHR endpoint actually returns, no request/response schema, and the crawled pages are empty beyond a wallet prompt. The EHR path is not even listed on the provider's landing page, making it effectively a stub listing.
Warnings
- —No documentation exists for the /api/v1/ehr/86 endpoint — it is not listed among the provider's advertised APIs
- —EHR (Electronic Health Record) data is typically subject to healthcare regulations (e.g., HIPAA); no compliance or privacy information is provided
- —All crawled subpages (docs, API, pricing, README) returned only 'Connect wallet' with no content
- —No request or response schema available — the data format is entirely unknown
- —The '86' in the path may be a specific record ID; it is unclear whether other IDs are valid or what data is returned
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units on Base network using USDChttps://lowpaymentfee.com/api/v1/ehr/86
- —The platform advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/86
- —Docs, API, pricing, and README pages returned only 'Connect wallet' with no substantive documentationhttps://lowpaymentfee.com/docs