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/64` 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 `/ehr/64` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its advertised categories, and no documentation describes its request or response schema.
Payment is handled via the x402 protocol on the Base network using USDC (contract `0x8335…2913`). The maximum amount required per call is 20,000 base units, which at 6 decimals equals $0.02 USD. The endpoint accepts POST requests and returns `application/json`. No API keys, rate limits, or upfront commitments are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Because the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, there is no information available about the request body format, expected parameters, or response structure for this specific endpoint. The endpoint is confirmed live (returns a proper 402 challenge), but its actual functionality and data content remain undocumented.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 64)
- —Integrating EHR data into agent workflows without managing API keys
- —Paying per-request for health data access using USDC on Base
Fit
Best for
- —Agents needing on-demand EHR data with crypto micropayments
- —Developers prototyping health data integrations without subscription commitments
- —x402-compatible clients on the Base network
Not for
- —Production healthcare applications requiring documented schemas and compliance guarantees
- —Users who need bulk or streaming EHR data access
- —Anyone needing HIPAA-compliant audit trails (no compliance documentation available)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/64 \
-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 zero documentation on request/response schema, no OpenAPI spec, and the /ehr/64 path is not listed on the provider's own landing page. The docs, pricing, and README pages are all empty (wallet-connect gates). This is effectively a stub listing with confirmed liveness but unknown functionality.
Warnings
- —The /ehr/64 endpoint is not listed among the provider's advertised APIs on the landing page — its purpose and data content are unverified.
- —No request or response schema is available; callers cannot know what parameters to send or what data to expect.
- —EHR (Electronic Health Record) data may be subject to healthcare regulations (e.g., HIPAA); no compliance documentation is provided.
- —All documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no content.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/64
- —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/64
- —The /ehr/64 endpoint is not listed among the provider's advertised API categorieshttps://lowpaymentfee.com