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/19` 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/19` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document EHR endpoints among its publicly advertised categories.
The endpoint is live and returns a valid x402 challenge (HTTP 402) requesting payment of 20,000 base units of USDC (0x8335…2913) on the Base network, which equals $0.02 per request (USDC uses 6 decimals). Payment is made via the x402 exact scheme with a 300-second timeout. No API keys, rate limits, or subscriptions are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what data the `/ehr/19` endpoint actually returns. The `outputSchema` in the challenge only confirms it accepts HTTP POST. Given the EHR naming convention, this may return health record data, but this cannot be verified from available materials. Users should exercise caution, especially given that EHR data may be subject to healthcare privacy regulations (e.g., HIPAA).
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR lookups into agent workflows without managing API keys
- —Accessing health data via crypto micropayments on Base
Fit
Best for
- —Developers needing keyless, pay-per-call access to EHR data
- —AI agents that can settle x402 payments autonomously on Base
- —Prototyping health data integrations without subscription commitments
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation and response schemas before integration
- —High-volume consumers who would benefit from bulk pricing or subscriptions
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/19 \
-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 the /ehr/19 resource actually returns. No OpenAPI schema, no request body format, no response examples. The EHR path is not listed on the provider's own landing page. This is effectively a stub listing.
Warnings
- —The /ehr/19 path is not listed among the provider's publicly advertised endpoints — its purpose and data content are unverified.
- —EHR (Electronic Health Record) data may be subject to healthcare privacy regulations such as HIPAA; compliance status is unknown.
- —No documentation, request schema, or response examples are available — the docs, API, pricing, and README pages all render only a wallet-connect prompt.
- —The provider site lists many endpoint categories but none related to health records, raising questions about whether this endpoint is actively maintained or a placeholder.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requesting 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/19
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/19
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompt with no additional contenthttps://lowpaymentfee.com/docs