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/31` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific resource at path `/ehr/31` is labeled "Premium API Access" but its exact functionality is unclear — the "ehr" path segment suggests Electronic Health Records, though no documentation confirms what data or service this endpoint returns.
The endpoint is live and responds with a valid x402 payment challenge. It accepts POST requests and settles on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum amount required is 20,000 base units of USDC, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing across all listed endpoints. Payment is sent to `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout.
Documentation is extremely sparse. The landing page lists many API categories but does not include `/api/v1/ehr/31` among them. The docs, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the endpoint actually returns. The input schema indicates HTTP POST with `discoverable: true`, but no request body schema or response schema is provided.
Capabilities
Use cases
- —Retrieving electronic health record data (record ID 31) via a single paid API call
- —Integrating health data into agent workflows without managing API keys
- —Programmatic access to EHR data settled via USDC on Base
Fit
Best for
- —Agents or applications needing on-demand EHR data access without subscription commitments
- —Developers experimenting with x402-protocol pay-per-call patterns
- —Low-volume health data retrieval where per-request pricing is economical
Not for
- —Production healthcare applications requiring documented schemas, SLAs, and compliance guarantees
- —High-volume bulk EHR data retrieval where per-request costs add up
- —Users who need clear documentation of request/response formats before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/31 \
-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 what the endpoint does, what request body it expects, or what it returns. The 'ehr' path is not listed among the platform's advertised APIs. No OpenAPI spec, no examples, no response schema — effectively a stub.
Warnings
- —The /api/v1/ehr/31 path is not listed among the platform's advertised endpoints, raising questions about its intended use or availability.
- —No request body schema or response schema is documented anywhere.
- —The 'ehr' path suggests Electronic Health Records, which is a regulated data category — no compliance or data-handling information is provided.
- —All documentation pages (docs, pricing, README) render only 'Connect wallet' with no usable content.
- —No way to verify what data this endpoint actually returns without making a paid request.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/31
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/31
- —The /api/v1/ehr/31 endpoint is not listed among the platform's advertised API categorieshttps://lowpaymentfee.com