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/4` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs settled in USDC on the Base network. The specific resource appears to be an Electronic Health Record (EHR) endpoint, though the provider's landing page does not list it among its publicly advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). The endpoint is live and returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0.02 USD per request).
The platform advertises a simple pricing model: $0.02 per request across all endpoints, with no API keys, no rate limits, no minimums, and instant access. Payment is handled via the x402 protocol's `exact` scheme on the Base L2 network, paying to address `0x1A2B...85F3` using the USDC contract at `0x8335...2913`. The endpoint accepts HTTP POST requests.
Documentation is extremely sparse — the 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 the EHR endpoint actually returns or what input it expects. The "EHR" designation (Electronic Health Record) suggests health data, but this cannot be confirmed from available materials. Users should exercise caution given the lack of documentation and the potentially regulated nature of health data.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR data into agent workflows without API key management
- —Accessing health-related data via crypto micropayments
Fit
Best for
- —Developers needing on-demand EHR data without subscription commitments
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping health data integrations with minimal setup
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Users who need detailed API documentation and request/response schemas before integration
- —Anyone unable to pay with USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/4 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the EHR endpoint accepts or returns. No OpenAPI schema, no examples, no description of the data. The endpoint is not even listed on the provider's own landing page. The potentially regulated health-data category adds risk.
Warnings
- —Endpoint /api/v1/ehr/4 is not listed among the provider's publicly advertised APIs — its availability and purpose are unclear.
- —No documentation exists for this endpoint: no request schema, no response schema, no examples.
- —'EHR' typically refers to Electronic Health Records, which may involve regulated health data (HIPAA, GDPR). The provider gives no compliance or data-source information.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/4
- —The platform advertises $0.02 per request with no API keys, no rate limits, no minimumshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/4
- —The provider lists Data & Analytics, AI & ML, Finance & Web3, and Infrastructure API categories but not EHRhttps://lowpaymentfee.com