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/35` 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 utility services. The specific `/ehr/35` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its documented APIs. The endpoint is live and returns a valid x402 challenge on POST requests.
Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 "exact" scheme. The maximum amount required is 20,000 base units, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing. No API keys, rate limits, or upfront commitments are advertised; callers simply attach an `X-PAYMENT` header with a valid payment proof.
Documentation is extremely sparse. The `/docs`, `/pricing`, `/api`, and `/README` pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what data the `/ehr/35` endpoint actually returns. The endpoint's purpose (EHR data) falls in a regulated domain (healthcare), which warrants caution. Without documentation of the input format or output schema, callers will need to experiment or contact the provider directly.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 35)
- —Integrating health data into agent workflows with per-request micropayments
- —Accessing EHR information without managing API keys or subscriptions
Fit
Best for
- —Developers needing on-demand EHR data access via crypto micropayments
- —AI agents that can settle x402 payments on Base
- —Projects that want keyless, pay-as-you-go health data endpoints
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Users who need detailed request/response schemas before integration
- —Callers who cannot settle USDC payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/35 \
-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 /ehr/35 actually returns, no OpenAPI spec, no request/response examples, and the endpoint is not even listed on the provider's own landing page. The regulated healthcare domain adds further concern.
Warnings
- —The /ehr/35 endpoint is not listed among the provider's documented APIs on the landing page — its purpose and data content are unknown.
- —EHR (Electronic Health Record) data is a regulated healthcare domain; no compliance or data-source information is provided.
- —All documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompt with no substantive content.
- —No request body schema or response schema is available; callers must experiment blind.
Citations
- —The platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The x402 challenge specifies maxAmountRequired of 20000 base units in USDC (6 decimals) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/ehr/35
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/ehr/35
- —Documentation pages (/docs, /pricing, /api, /README) show only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs