x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/23` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific resource at path `/ehr/23` is labeled "Premium API Access" in the x402 challenge but its exact data domain is unclear — the "ehr" path segment suggests Electronic Health Records, though the provider's landing page does not list this endpoint among its documented APIs. The endpoint is live and returns 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 for USDC equals $0.02 per request — consistent with the provider's advertised flat $0.02/request pricing across all endpoints. No API keys, rate limits, or subscriptions are required; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The provider's docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema, and no description of what data this endpoint actually returns. The `outputSchema` in the challenge confirms it accepts HTTP POST but provides no field-level detail. Prospective users should treat this as an exploratory endpoint until the provider publishes proper documentation.
Capabilities
Use cases
- —Retrieving health record data (EHR) on a per-request payment basis
- —Agent-driven data access without pre-registration or API keys
- —Programmatic micropayment-gated data retrieval on Base L2
Fit
Best for
- —Developers exploring x402-protocol pay-per-call patterns
- —Agents that need keyless, on-demand API access settled in USDC
- —Low-volume or experimental access to gated data endpoints
Not for
- —Production healthcare applications requiring documented, compliant EHR APIs
- —High-volume bulk data retrieval where per-request pricing is inefficient
- —Users who need detailed API documentation and response schemas before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/23 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific resource (/ehr/23) is not listed on the provider's own landing page. The purpose and data returned are essentially unknown.
Warnings
- —The /ehr/ path suggests Electronic Health Records — a regulated data category — but no compliance or data-source information is provided.
- —This specific endpoint (/api/v1/ehr/23) is not listed among the provider's documented APIs on the landing page.
- —No request or response schema is available; callers cannot know what fields to send or expect back.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no technical content.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/23
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/23
- —Provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The /api/v1/ehr/23 endpoint is not listed among the provider's documented API categorieshttps://lowpaymentfee.com