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/57` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific resource at path `/ehr/57` is labeled "Premium API Access" but its exact functionality is unclear — the "ehr" path segment suggests Electronic Health Records, though no documentation confirms what data or service is returned. The endpoint is live and responds with 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 site-wide $0.02/request pricing advertised on the landing page. No API keys are needed; access is granted by including a valid `X-PAYMENT` header with a signed payment proof. The timeout window is 300 seconds.
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 `/api/v1/ehr/57` endpoint actually returns. The `57` in the path may be a resource ID, but this is unconfirmed. Prospective users should exercise caution given the lack of documentation and the potentially sensitive nature of EHR-related data.
Capabilities
Use cases
- —Retrieving health record data (if confirmed as EHR) via a single pay-per-request call
- —Agent-driven data retrieval without pre-registration or API key management
- —Programmatic access to premium data behind x402 micropayment gating
Fit
Best for
- —Developers experimenting with x402 pay-per-request protocols
- —Agents that need keyless, on-demand API access settled in USDC on Base
- —Low-volume or sporadic access patterns where $0.02/call is cost-effective
Not for
- —Production healthcare applications requiring documented, compliant EHR APIs
- —High-volume bulk data retrieval where per-request pricing adds up
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/57 \
-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 there is zero documentation on what the /ehr/57 resource actually returns. No OpenAPI schema, no request/response examples, and all doc pages render only 'Connect wallet'. The endpoint purpose is inferred solely from the URL path.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —The 'ehr' path segment suggests Electronic Health Records, which is a regulated data category; no compliance or data-source information is provided
- —No request body schema or response schema is documented; callers cannot know what to send or expect back
- —The '/57' path suffix may be a hardcoded resource ID; it is unclear if other IDs are valid
- —Potentially sensitive health data with no visible privacy policy or terms of service
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/57
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/57