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/26` 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/26` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document this particular endpoint. The platform advertises $0.02 per request across all endpoints, and the x402 challenge confirms a maxAmountRequired of 20,000 base units of USDC (6 decimals) on Base network, which equals $0.02.
Payment is handled via the x402 exact-payment scheme: callers send a signed USDC payment in the `X-PAYMENT` header and receive the JSON response directly — no API keys, accounts, or rate limits. The endpoint accepts POST requests and returns `application/json`. The pay-to address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet, settling in USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`).
Documentation is extremely sparse. The crawled docs, pricing, and API 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 data the `/ehr/26` endpoint actually returns or what input it expects. The EHR designation raises potential concerns about health data regulation (HIPAA, etc.), but no compliance information is provided.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 26)
- —Integrating EHR data into agent workflows with per-request crypto payments
- —Accessing health data without managing API keys or subscriptions
Fit
Best for
- —Agents needing on-demand EHR data with crypto micropayments
- —Developers prototyping health data integrations without signup
- —x402-compatible clients on Base network
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Users who need detailed API documentation or schema validation before integration
- —Non-crypto callers who cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/26 \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no request/response schema, no examples, and the specific /ehr/26 path is not listed on the provider's landing page. The EHR designation without any compliance or content documentation is a significant concern.
Warnings
- —The /api/v1/ehr/26 path is not listed among the provider's advertised endpoints on the landing page — its purpose and data content are unknown.
- —No request body schema or response schema is documented anywhere; callers must guess at the expected input.
- —EHR (Electronic Health Record) data may be subject to HIPAA or other health data regulations — no compliance information is provided.
- —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no substantive content.
- —No OpenAPI spec or ai-plugin manifest is available.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/26
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/26
- —The /ehr/26 endpoint is not listed among the provider's advertised API categorieshttps://lowpaymentfee.com