x402-gated EHR endpoint on Base, pay $0.02 per request in USDC with no API keys.
What it does
This endpoint at `/api/v1/ehr/13` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific `/ehr/13` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its documented API categories. The endpoint is live and returns a valid x402 challenge on POST.
Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the "exact" scheme. The `maxAmountRequired` is 20,000 base units, which at 6 decimals equals $0.02 per request — consistent with the provider's uniform $0.02/request pricing across all listed endpoints. No API keys are required; access is granted by attaching a valid `X-PAYMENT` header with a signed payment proof. The challenge specifies a 300-second timeout window.
Because the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" stub with no substantive content, there is no schema documentation, example request/response, or detailed description of what the `/ehr/13` endpoint actually returns. The endpoint's purpose and data format must be inferred from its path alone, which is a significant limitation.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 13)
- —Agent-driven healthcare data access with per-call micropayments
- —Integrating EHR data into workflows without managing API keys or subscriptions
Fit
Best for
- —Developers needing on-demand EHR data access without subscription commitments
- —AI agents that can autonomously pay for health data per request
- —Prototyping healthcare integrations with minimal setup
Not for
- —Production healthcare systems requiring HIPAA-compliant audit trails and BAAs (no compliance documentation available)
- —Bulk retrieval of large EHR datasets (pay-per-request model at $0.02/call adds up)
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/13 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the /ehr/13 endpoint accepts or returns. All doc pages are stubs. The endpoint is not even listed on the provider's own landing page, and the health/EHR domain raises regulatory concerns without any compliance information.
Warnings
- —The /ehr/13 path is not listed among the provider's documented APIs on the landing page — its availability and purpose are uncertain.
- —No request or response schema documentation exists; all doc pages return only 'Connect wallet' stubs.
- —EHR data may be subject to healthcare regulations (HIPAA, GDPR health data provisions) — no compliance or data-handling documentation is provided.
- —The nature of the data behind this endpoint is entirely unknown; 'EHR' in the path is the only clue.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/13
- —The provider advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/13
- —Documentation pages (/docs, /api, /pricing, /README) return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs