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/41` is part of the lowpaymentfee.com platform, which offers a broad catalog of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific `/ehr/41` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document this particular endpoint. 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 uniform $0.02/request pricing advertised across all endpoints on the site. No API keys, rate limits, or upfront commitments are required; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no description of what data the `/ehr/41` endpoint actually returns. The endpoint accepts POST requests and returns `application/json`, but the exact input parameters and output fields are unknown.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR data into agent workflows without managing API keys
- —Accessing health data via crypto micropayments on Base
Fit
Best for
- —Developers who want keyless, pay-per-call access to health data
- —AI agents that can settle x402 payments autonomously on Base
- —Prototyping integrations that need EHR data without subscription commitments
Not for
- —Production healthcare systems requiring HIPAA-compliant, documented APIs with SLAs
- —Users who need detailed schema documentation before integrating
- —Anyone unable to pay with USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/41 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what /api/v1/ehr/41 actually does, what inputs it expects, or what it returns. No OpenAPI spec, no examples, no request/response schemas. The EHR path is not even listed on the provider's own landing page. This is effectively a stub listing.
Warnings
- —The /ehr/41 endpoint is not listed on the provider's own landing page — its purpose and data content are unknown.
- —No documentation exists: docs, pricing, API, and README pages all show only 'Connect wallet'.
- —No request or response schema is available; input parameters are completely unknown.
- —EHR data may be subject to healthcare regulations (e.g., HIPAA); the provider gives no compliance information.
- —The provider offers dozens of endpoints at a uniform $0.02 price with no visible documentation — exercise caution regarding data quality and legitimacy.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/41
- —Uniform pricing of $0.02 per request across all endpoints, no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/ehr/41
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs