x402-gated EHR endpoint on Base, pay-per-call with USDC — part of a broader API marketplace.
What it does
This endpoint (`/api/v1/ehr/56`) is one of many pay-per-request APIs hosted on lowpaymentfee.com, a marketplace of x402-protocol endpoints settled in USDC on the Base network. The specific endpoint appears to serve electronic health record (EHR) data, though the crawled documentation provides no details about the schema, fields, or data source behind this particular resource. The site advertises a flat $0.02 per request across all its endpoints, and the x402 challenge confirms a maxAmountRequired of 20,000 base units of USDC (0.02 USDC, i.e. $0.02) on Base.
The broader lowpaymentfee.com platform lists endpoints across several categories: data & analytics (metrics, reports, export, insights), AI & ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints follow the same x402 payment model with no API keys, no rate limits, and no minimum commitments.
Important caveats: the `/api/v1/ehr/56` path is not listed on the site's public landing page among the advertised APIs, and no documentation exists describing what EHR data is returned, what the `56` identifier refers to, or what input the POST body expects. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. This endpoint should be treated as poorly documented and potentially experimental.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR lookups into agent workflows without API key management
- —Programmatic access to health data settled via crypto micropayments
Fit
Best for
- —Developers needing pay-as-you-go EHR data access without subscriptions
- —AI agents that can settle x402 payments on Base
- —Prototyping health data integrations with minimal onboarding
Not for
- —Production healthcare systems requiring HIPAA-compliant, well-documented APIs
- —Users who need detailed schema documentation before integration
- —Anyone needing non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/56 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge), but there is zero documentation on what this EHR endpoint does, what input it expects, or what it returns. The /ehr/56 path is not even listed among the site's advertised APIs. No OpenAPI spec, no examples, no schema beyond the x402 challenge metadata. This is effectively a stub listing.
Warnings
- —The /api/v1/ehr/56 endpoint is not listed on the provider's public landing page — it may be experimental or unlisted.
- —No documentation exists for this endpoint: input schema, output schema, and data source are all unknown.
- —EHR (Electronic Health Record) data may be subject to HIPAA and other health data regulations — no compliance information is provided.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
- —The meaning of the identifier '56' in the path is unexplained.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/56
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/56
- —Site advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The /api/v1/ehr/56 path is not listed among the publicly advertised endpoints on the landing pagehttps://lowpaymentfee.com