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/2` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs settled in USDC on the Base network. The specific endpoint appears to serve electronic health record (EHR) data, though the crawled documentation provides no details about the request format, response schema, or what health data is actually returned. The platform advertises a uniform $0.02 per request pricing model across all its endpoints.
The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is settled on-chain via USDC (contract `0x8335...2913` on Base) using the "exact" scheme, with a `maxAmountRequired` of 20000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys or rate limits are advertised — access is gated purely by the x402 payment header. The timeout for payment settlement is 300 seconds.
Important caveats: the endpoint's actual functionality is unclear. The title "Premium API Access" is generic, and the path `/api/v1/ehr/2` suggests electronic health records but no documentation, input schema, or sample responses are available. The broader platform lists many endpoint categories (analytics, AI/ML, finance, infrastructure) but the EHR endpoint is not listed among them on the landing page. Prospective users should treat this as an under-documented endpoint and test carefully before relying on it.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR lookups into agent workflows without managing API keys
- —Accessing health data via crypto-native micropayments on Base
Fit
Best for
- —Developers wanting keyless, pay-per-use access to health data
- —Agent-based systems that can settle x402 payments automatically
- —Prototyping integrations that need on-demand EHR data
Not for
- —Production healthcare systems requiring HIPAA-compliant, documented APIs
- —Users who need detailed schema documentation before integration
- —High-volume use cases where per-request pricing is cost-prohibitive
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/2 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on what the EHR endpoint actually does, what inputs it expects, or what it returns. The endpoint is not even listed on the provider's own landing page. No OpenAPI spec, no examples, no response schema.
Warnings
- —No documentation exists for the /api/v1/ehr/2 endpoint — its purpose and data format are unknown
- —The EHR endpoint is not listed among the provider's advertised APIs on the landing page
- —If this serves actual health records, regulatory compliance (HIPAA, GDPR) is a serious concern and is not addressed anywhere
- —All non-homepage crawled pages returned only 'Connect wallet' with no useful content
- —No input or output schema is available — callers must discover the API by trial and error
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/2
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/2