x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/45` 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/45` is labeled "Premium API Access" in the x402 challenge but lacks further documentation about what data it returns. The provider's homepage lists categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities, all priced at $0.02 per request — however this particular `/ehr/45` endpoint is not listed among them and its pricing differs (see below).
The x402 challenge confirms the endpoint is live, accepting POST requests and requiring payment of up to 20,000 base units of USDC (contract `0x8335…2913` on Base). Since USDC uses 6 decimals, this equals $0.02 per request, consistent with the platform's advertised flat pricing. Payment is made via the x402 exact scheme with a 300-second timeout. No API key or account registration is needed; callers authenticate purely through the X-PAYMENT header.
Documentation is extremely sparse. The `/docs`, `/api`, `/pricing`, and `/README` pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no explanation of what "EHR" refers to in this context (it commonly abbreviates Electronic Health Record, but this is unconfirmed). The endpoint's purpose, expected input body, and response format are unknown.
Capabilities
Use cases
- —Accessing EHR or premium data records via a single paid POST request
- —Agent-driven data retrieval with automatic USDC micropayments on Base
- —Integrating pay-per-use data endpoints without managing API keys or subscriptions
Fit
Best for
- —Developers or agents wanting keyless, pay-per-call data access on Base
- —x402-compatible agents that can settle USDC micropayments automatically
- —Prototyping integrations against low-cost pay-per-request endpoints
Not for
- —Production healthcare/EHR workflows requiring documented schemas and compliance guarantees
- —Users who need detailed API documentation or OpenAPI specs before integration
- —High-volume use cases where per-request pricing may not be economical
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/45 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-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 this endpoint does, what inputs it expects, or what it returns. The 'ehr/45' path is not listed on the provider's homepage, and all doc pages are empty. This is effectively a stub listing.
Warnings
- —The /ehr/45 endpoint is not listed among the provider's advertised APIs — its purpose is unknown.
- —No request or response schema is available; callers cannot know what to send or expect back.
- —'EHR' may refer to Electronic Health Records, which is a regulated data category — but this is unconfirmed.
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content.
Citations
- —The x402 challenge returns 402 with maxAmountRequired 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/45
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/45
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs