x402-gated EHR endpoint on Base, pay $0.02 per request in USDC — no API keys required.
What it does
This endpoint at lowpaymentfee.com provides premium API access at the path `/api/v1/ehr/88`. It is part of a broader platform that offers dozens of x402-gated endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/ehr/88` appears to serve electronic health record (EHR) data based on the URL path, though the provider's landing page does not explicitly list or document this particular route. The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is "exact" scheme, requiring up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the EHR endpoint returns or what input it expects. The endpoint is confirmed live via its 402 challenge, but without documentation it is difficult to know what data it actually provides or what POST body it requires.
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
- —Agents or developers needing on-demand EHR data without subscription commitments
- —Crypto-native applications that can settle micropayments in USDC on Base
- —Prototyping health-data integrations with zero onboarding friction
Not for
- —Production healthcare systems requiring HIPAA-compliant, documented APIs with SLAs
- —Users who need detailed schema documentation or example payloads before integrating
- —High-volume batch EHR retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/88 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Endpoint
Quality
The endpoint is confirmed live via its 402 challenge, but there is zero documentation — no OpenAPI spec, no request/response examples, no description of what the EHR endpoint actually returns. The docs pages are empty. The endpoint path suggests health data, which is a regulated category, adding risk. Effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all render only a wallet-connect prompt with no content.
- —The endpoint path suggests electronic health record data, which is a regulated/sensitive category (HIPAA, GDPR). No compliance or data-handling information is provided.
- —No OpenAPI schema, no request body specification, and no response examples exist in any crawled material.
- —This specific endpoint (/api/v1/ehr/88) is not listed on the provider's landing page among their advertised APIs.
- —The hardcoded ID '88' in the path is unexplained — unclear if this is a record ID, a resource type, or a versioning artifact.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/ehr/88
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/ehr/88
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompt with no substantive documentation.https://lowpaymentfee.com/docs