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/24` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs settled in USDC on the Base network. The specific endpoint appears to serve Electronic Health Record (EHR) data, though the provider's landing page does not list this particular path among its documented API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). The endpoint is live and returns a valid x402 challenge.
Pricing is $0.02 per request (maxAmountRequired of 20,000 base units of USDC, which has 6 decimals = $0.02). Payment is made via the x402 exact scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. 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, pricing, and README pages all returned only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no description of request/response formats for this EHR endpoint, and no indication of what data resource ID 24 represents. The endpoint accepts POST requests and returns `application/json`. Without further documentation, callers will need to experiment to determine the expected request body and response structure.
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 experimenting with x402-protocol health data endpoints
- —Crypto-native applications that can pay per call in USDC on Base
Not for
- —Production healthcare systems requiring documented, HIPAA-compliant APIs with SLAs
- —Users who need detailed API documentation and schema definitions before integrating
- —High-volume consumers who would benefit from bulk pricing or subscriptions
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/24 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what this EHR endpoint does, what request body it expects, or what it returns. The /ehr/ path is not listed on the provider's own landing page. No OpenAPI schema, no examples, no docs — effectively a stub.
Warnings
- —The /api/v1/ehr/24 path is not listed among the provider's documented API categories on the landing page.
- —No documentation exists for request or response format — callers must experiment.
- —EHR (Electronic Health Record) data may be subject to healthcare regulations (e.g., HIPAA); no compliance information is provided.
- —Docs, pricing, and README pages returned only 'Connect wallet' with no usable content.
- —The nature and provenance of the health data served is completely unknown.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/24
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/24
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The landing page lists Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categories but does not list an EHR endpointhttps://lowpaymentfee.com