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/16` 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 appears to be an Electronic Health Record (EHR) endpoint, though the provider's landing page does not list it among its publicly advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). The endpoint is live and returns a valid x402 challenge with a maximum cost of 20,000 base units of USDC (0.02 USD) per request.
The platform advertises a simple pricing model: $0.02 per request with no API keys, no rate limits, no minimums, and no commitments. Payment is handled via the x402 protocol's `exact` scheme on the Base L2 network, settling to USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The endpoint accepts HTTP POST requests and returns `application/json` responses.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what the `/api/v1/ehr/16` endpoint actually returns or what input it expects. The "EHR" path segment suggests electronic health records, but this is unconfirmed and the `16` path parameter's meaning is unknown.
Capabilities
Use cases
- —Retrieving electronic health record data via a single paid API call
- —Integrating EHR data into agent workflows without managing API keys
- —Programmatic access to health record information settled on-chain
Fit
Best for
- —Developers needing keyless, pay-per-call access to EHR data
- —AI agents with Base USDC wallets that need health data
- —Prototyping integrations that require on-demand health record lookups
Not for
- —Production healthcare applications requiring documented, HIPAA-compliant APIs
- —Users who need detailed schema documentation or guaranteed SLAs
- —Bulk retrieval of large health record datasets
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/16 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the EHR endpoint does, what inputs it expects, or what it returns. The endpoint is not listed on the provider's own landing page. No OpenAPI schema, no examples, and all doc pages are empty. This is effectively a stub listing.
Warnings
- —The /api/v1/ehr/16 endpoint is not listed among the provider's publicly advertised APIs — its purpose and data source are unverified.
- —EHR (Electronic Health Record) data may be subject to healthcare regulations (e.g., HIPAA). No compliance information is provided.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no usable content.
- —No request or response schema is available; input format and output structure are completely unknown.
- —The meaning of the path parameter '16' is undocumented.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/16
- —The platform advertises $0.02 per request with no API keys, no rate limits, and no minimumshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/16
- —Documentation pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs
- —The /api/v1/ehr/16 endpoint is not listed among the provider's publicly advertised API categorieshttps://lowpaymentfee.com