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/54` is part of the lowpaymentfee.com platform, which offers a broad catalog of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific resource at path `/ehr/54` 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 this endpoint returns.
The endpoint is live and responds with a valid x402 challenge on POST. Payment is settled on the Base network using USDC (contract `0x8335…2913`) with a max amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). This matches the platform's advertised flat rate of $0.02 per request across all endpoints. The platform advertises no API keys, no rate limits, and instant access — you simply attach an x402 payment header to each call.
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/54` endpoint actually returns. The output schema in the x402 challenge only specifies that the input method is HTTP POST and the response MIME type is `application/json`. Prospective callers should be aware that the exact request body format and response structure are undocumented.
Capabilities
Use cases
- —Accessing health record data on a per-request payment basis without subscription or API key management
- —Integrating pay-per-call EHR data into agent workflows via x402 protocol
- —Programmatic retrieval of structured health information settled in USDC on Base
Fit
Best for
- —Developers wanting zero-signup, pay-as-you-go API access
- —AI agents that can settle x402 payments autonomously on Base
- —Projects needing occasional EHR data without committing to a subscription
Not for
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Applications requiring bulk or high-throughput health data pipelines with predictable pricing
- —Regulated healthcare workflows that require HIPAA-compliant, audited data sources
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/54 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what /api/v1/ehr/54 actually does, what request body it expects, or what it returns. No OpenAPI spec, no examples, and the docs pages are empty. The 'ehr' path is suggestive but unconfirmed. This is effectively a stub listing.
Warnings
- —The exact purpose and data returned by /api/v1/ehr/54 are completely undocumented — 'ehr' may imply Electronic Health Records but this is unconfirmed.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no substantive content.
- —If this endpoint does serve health data, it may be subject to HIPAA or other healthcare data regulations — no compliance information is provided.
- —No request body schema or response schema is documented anywhere.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/54
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/54
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs