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/68` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific `/ehr/68` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its documented API categories. The endpoint is live and returns a valid x402 challenge on POST.
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. No API keys, rate limits, or upfront commitments are advertised; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation beyond the landing page is extremely thin — the `/docs`, `/pricing`, `/api`, and `/README` pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema, and no description of what the `/ehr/68` resource actually returns. Prospective callers should be aware that the EHR endpoint is not listed on the provider's public API catalog, and the nature of the data it serves is unclear.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR lookups into agent workflows without managing API keys
- —Paying for health data access with USDC on Base L2
Fit
Best for
- —Developers needing keyless, pay-per-call access to an EHR resource
- —AI agents that can settle x402 payments on Base
- —Prototyping health-data integrations without subscription commitments
Not for
- —Production healthcare applications requiring HIPAA-compliant, well-documented APIs
- —Users who need detailed request/response schemas before integration
- —Anyone needing bulk or streaming EHR data at scale
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/68 \
-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 no documentation, no OpenAPI spec, no request/response schema, and the /ehr/68 path is not listed on the provider's own site. The actual data returned is unknown, making this effectively a stub listing.
Warnings
- —The /ehr/68 endpoint is not listed among the provider's publicly advertised APIs — its existence and purpose are unverified beyond the 402 challenge.
- —No request or response schema is available; callers cannot know what to send or what they will receive.
- —All documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompt with no technical content.
- —EHR data may be subject to healthcare privacy regulations (e.g., HIPAA); the provider gives no compliance information.
- —The nature and provenance of the health data served is completely undocumented.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/68
- —Platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/ehr/68
- —Documentation pages /docs, /pricing, /api, /README show only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs