x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/18` is part of the lowpaymentfee.com platform, which offers a variety of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific `/ehr/18` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its publicly advertised APIs, and no documentation or schema details are available for it.
The endpoint is live and returns a valid x402 challenge on POST. Payment is settled on the Base network using USDC (contract `0x8335…2913`) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). The platform advertises a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and instant access. The x402 challenge specifies an `exact` payment scheme with a 300-second timeout.
Because the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, there is no information about request/response schemas, expected input parameters, or what data this EHR endpoint actually returns. The endpoint name and path suggest healthcare-related data, but this cannot be confirmed from available sources. Users should exercise caution given the lack of documentation and the sensitive nature of EHR data.
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
- —Agents needing on-demand EHR data access without subscription commitments
- —Developers prototyping health data integrations with minimal setup
- —x402-compatible wallets and agents on the Base network
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Use cases needing detailed schema validation or guaranteed SLAs
- —Users who cannot pay with USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/18 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schemas, no description of what the EHR endpoint returns, and the docs/pricing/README pages are all empty. The endpoint is not even listed on the provider's own landing page. This is effectively a stub listing.
Warnings
- —The /ehr/18 endpoint is not listed among the provider's publicly advertised APIs — its purpose and data content are unknown.
- —No request or response schema is documented; input parameters are entirely unclear.
- —EHR (Electronic Health Record) data is typically subject to healthcare regulations (e.g., HIPAA). No compliance information is provided.
- —All documentation pages (/docs, /api, /pricing, /README) returned no useful content — only a 'Connect wallet' prompt.
- —The nature and provenance of the health data served by this endpoint cannot be verified.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/18
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/18
- —Documentation pages (/docs, /api, /pricing, /README) contain only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs