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/39` 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 `/api/v1/ehr/39` is listed under the title "Premium API Access" but its exact functionality is unclear — the path suggests an Electronic Health Record (EHR) resource with ID 39, though no documentation describes the request or response schema for this endpoint.
Payment is handled via the x402 protocol on the Base network. The challenge advertises a maximum cost of 20,000 base units of USDC (contract `0x8335…2913`, 6 decimals), which equals $0.02 per request. The platform's landing page confirms a flat $0.02/request pricing model across all endpoints with no API keys, no rate limits, and no minimum commitments. Payments settle to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout.
Documentation is extremely sparse. The `/docs`, `/api`, `/pricing`, and `/README` pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema` indicating an HTTP POST method, and no description of what data this endpoint actually returns. Prospective users should be aware that the "EHR" path component may imply health data, which could carry regulatory implications (HIPAA, etc.), but there is no information to confirm or deny this.
Capabilities
Use cases
- —Retrieving EHR or health-related data records via a single paid API call
- —Integrating pay-per-request data access into agent workflows without managing API keys
- —Programmatic access to record ID 39 from the lowpaymentfee.com EHR collection
Fit
Best for
- —Agents or developers who want keyless, pay-per-call data access on Base
- —x402-compatible clients that can settle USDC micropayments automatically
- —Quick one-off data retrieval without subscription commitments
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —Applications requiring HIPAA-compliant health data pipelines (compliance status unknown)
- —High-volume batch retrieval where per-request pricing may add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/39 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on what this endpoint accepts or returns. No OpenAPI spec, no examples, no request/response schema. The EHR path is unexplained, and all doc pages render only a wallet-connect prompt.
Warnings
- —No documentation available — /docs, /pricing, /README all show only 'Connect wallet' with no content
- —No request or response schema provided; the endpoint's actual functionality is unknown
- —The 'ehr' path component suggests health data, which may carry regulatory obligations (e.g., HIPAA) — compliance status is completely undocumented
- —This appears to be a generic demo/template platform; actual data quality and reliability are unverified
Citations
- —Flat $0.02/request pricing, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired 20000 USDC base units (= $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/ehr/39
- —USDC contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/39