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/85` 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 at path `/ehr/85` is labeled "Premium API Access" in the x402 challenge but its exact functionality is unclear — the "ehr" path segment suggests Electronic Health Records, though the provider's landing page does not list or document this particular endpoint among its advertised categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure).
The endpoint is live and returns a valid x402 challenge (HTTP 402) requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is via the x402 "exact" scheme, with a 300-second timeout. The platform advertises a flat $0.02/request pricing across all endpoints, no API keys, no rate limits, and instant access.
Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no description of what data this endpoint actually returns. The "ehr/85" path is not mentioned anywhere on the site's landing page. Without documentation or example responses, the actual payload and use case remain unknown.
Capabilities
Use cases
- —Retrieving health record data (EHR) via a single pay-per-call request
- —Programmatic access to structured health information without subscription
- —Agent-driven medical data retrieval settled in USDC on Base
Fit
Best for
- —Developers needing low-cost, keyless access to health record data
- —AI agents that can settle x402 micropayments on Base
- —Prototyping health data integrations without subscription commitments
Not for
- —Production healthcare systems requiring HIPAA-compliant, documented APIs
- —Users who need detailed API documentation and response schemas before integrating
- —Anyone needing non-crypto payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/85 \
-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 /api/v1/ehr/85 actually does or returns. No OpenAPI spec, no request/response schema, no examples, and the endpoint isn't even listed on the provider's own landing page. Effectively a stub.
Warnings
- —The /ehr/85 endpoint is not listed or documented anywhere on the provider's landing page or docs.
- —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no content.
- —The 'ehr' path suggests Electronic Health Records, which is a regulated data category — no compliance or privacy information is provided.
- —No request body schema or response schema is available; actual functionality is unknown.
- —No OpenAPI specification found.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/85
- —The platform advertises $0.02/request pricing, no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/ehr/85
- —Documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs