x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/89` is part of the lowpaymentfee.com platform, which offers a collection of x402 protocol-gated APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific endpoint being listed appears to serve Electronic Health Record (EHR) data, though the provider's landing page does not explicitly document this particular route — it is not among the publicly listed APIs on the homepage. The endpoint is live and returns a valid x402 payment challenge.
Payment is settled on the Base network using USDC (contract `0x8335...2913`). The x402 challenge advertises a `maxAmountRequired` of 20,000 base units, which at 6 decimals for USDC equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing. The endpoint accepts POST requests and returns `application/json`. No API keys, rate limits, or subscriptions are required; each call is individually paid via the x402 payment header.
Because the `/api/v1/ehr/89` path is not documented on the provider's public pages, the exact request schema, response fields, and data source are unknown. The "89" in the path likely represents a resource identifier. Users should be aware that EHR data may be subject to healthcare privacy regulations (e.g., HIPAA in the US). Without documentation clarifying what data is returned and its provenance, caution is warranted.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource ID
- —Integrating EHR data into healthcare applications via pay-per-call access
- —Agent-driven health data lookups without managing API keys or subscriptions
Fit
Best for
- —Developers needing on-demand EHR data access without subscription commitments
- —AI agents that can settle x402 payments on Base with USDC
- —Prototyping healthcare data integrations with minimal setup
Not for
- —Production healthcare systems requiring HIPAA-compliant, audited data pipelines
- —Use cases needing bulk or batch EHR data retrieval at scale
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/89 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but the specific /api/v1/ehr/89 route is not documented anywhere on the provider's site. No request/response schema, no examples, and no explanation of what EHR data is served. The crawled docs/pricing/README pages are all blank beyond a wallet-connect prompt. Effectively a stub listing.
Warnings
- —The /api/v1/ehr/89 endpoint is not listed among the provider's publicly documented APIs — its purpose and data source are unverified.
- —EHR (Electronic Health Record) data may be subject to healthcare privacy regulations such as HIPAA; the provider offers no compliance documentation.
- —All documentation pages (/docs, /pricing, /README, /api) returned only a 'Connect wallet' prompt with no actual content.
- —No request or response schema is available; input format and output fields are unknown.
Citations
- —The platform advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/ehr/89
- —The /api/v1/ehr/89 endpoint is not among the APIs listed on the provider's homepage.https://lowpaymentfee.com