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/8` is part of the lowpaymentfee.com platform, which offers a variety of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific `/ehr/8` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not document this particular endpoint in its public catalog — it lists analytics, AI, finance, and utility endpoints but not EHR routes. The endpoint is live and returns a valid x402 challenge.
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 advertised flat $0.02/request pricing across all endpoints. The x402 flow means no API keys or accounts are needed: callers attach an `X-PAYMENT` header with a signed payment proof and receive the response directly.
Because the `/api/v1/ehr/8` path is not listed on the provider's public catalog and the crawled docs/pricing/README pages all render only a "Connect wallet" stub with no additional documentation, the actual response schema and data content of this endpoint are unknown. It may return health-record-related JSON, but this is inferred solely from the URL path. Treat with caution, especially given potential regulatory implications of health data.
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 needing on-demand EHR data without subscription commitments
- —Developers experimenting with x402 pay-per-call health data access
- —Crypto-native applications that settle in USDC on Base
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation and guaranteed SLAs before integrating
- —Bulk EHR data retrieval where per-request pricing would be cost-prohibitive
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/8 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but the /ehr/8 path is not documented anywhere on the provider's site. No request/response schema, no docs beyond a wallet-connect stub, and the EHR designation is inferred purely from the URL. Potential health-data regulatory concerns add risk.
Warnings
- —The /api/v1/ehr/8 endpoint is NOT listed in the provider's public API catalog — its purpose and response format are unknown.
- —EHR (Electronic Health Record) data may be subject to HIPAA or equivalent health-data regulations; no compliance information is provided.
- —All documentation pages (/docs, /pricing, /README, /api) render only a 'Connect wallet' stub with no usable content.
- —No request body schema or response schema is documented anywhere.
Citations
- —The provider advertises $0.02/request flat pricing with no API keys, no rate limits, and settlement on Base network.https://lowpaymentfee.com
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC (6 decimals) = $0.02, on the Base network.https://lowpaymentfee.com/api/v1/ehr/8
- —The /api/v1/ehr/8 path is not listed among the provider's publicly cataloged endpoints.https://lowpaymentfee.com