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/7` 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 (0x8335…2913 on Base), which equals $0.02 per request given USDC's 6 decimals.
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 X-PAYMENT header using the "exact" scheme on Base. The endpoint accepts POST requests and returns application/json responses. A 300-second payment timeout is configured.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive 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 nature of the data (whether synthetic, demo, or real health records) is entirely unclear from available materials.
Capabilities
Use cases
- —Retrieving electronic health record data via a pay-per-call model
- —Integrating EHR data into agent workflows without managing API keys
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents needing on-demand EHR data access without subscription commitments
- —Low-volume health data retrieval at $0.02 per call
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —High-volume bulk EHR data extraction (no documented batch support)
- —Users who need detailed API documentation or schema definitions before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/7 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"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 /docs and related pages are empty. The endpoint isn't even listed on the provider's own landing page. This is effectively a stub listing.
Warnings
- —The EHR endpoint is not listed among the provider's publicly advertised APIs — its purpose and data contents are unknown.
- —No documentation exists: /docs, /pricing, /api, and /README all render only a wallet-connect prompt.
- —No request or response schema is available; callers cannot know what to send or expect back.
- —EHR data may involve regulated health information — compliance status (HIPAA, etc.) is completely undocumented.
- —The nature of the data (real, synthetic, demo) is unclear.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/7
- —Platform pricing is $0.02 per request with no API keys, no rate limits, no minimumshttps://lowpaymentfee.com
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/7
- —Documentation pages (/docs, /pricing, /api, /README) render only a Connect wallet prompthttps://lowpaymentfee.com/docs