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/93` 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/93` 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 particular endpoint returns.
The endpoint is live and responds with a valid x402 challenge (HTTP 402) on POST. Payment is settled on the Base network using USDC (contract `0x8335…2913`) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). This matches the site-wide advertised pricing of $0.02 per request. The platform advertises no API keys, no rate limits, and instant access — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
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 `/api/v1/ehr/93` endpoint actually returns. The `outputSchema` in the challenge only confirms it accepts HTTP POST. Without further documentation, callers must experiment to discover the expected request body and response format.
Capabilities
Use cases
- —Accessing health record data (EHR) on a per-request payment basis without needing an API key
- —Integrating pay-per-call data endpoints into agent workflows using x402 protocol
- —Programmatic retrieval of record ID 93 from the EHR dataset
Fit
Best for
- —Developers experimenting with x402 pay-per-call protocols
- —Agents that need keyless, on-demand API access settled in USDC on Base
- —Low-volume or exploratory access to EHR-style data without subscription commitments
Not for
- —Production healthcare applications requiring HIPAA-compliant, well-documented EHR APIs
- —High-volume bulk data retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation and response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/93 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the /ehr/93 endpoint actually does, no request/response schema, and no examples. The docs pages are empty. The 'ehr' path is unexplained, making this effectively a stub listing.
Warnings
- —The 'ehr' path segment suggests Electronic Health Records but no documentation confirms this — the actual data returned is unknown.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content.
- —No OpenAPI schema, no request body specification, and no response examples are available.
- —If this endpoint does serve health data, it may be subject to HIPAA or other health-data regulations — no compliance information is provided.
- —The endpoint path includes a hardcoded ID (93); it is unclear whether other IDs are valid or what they represent.
Citations
- —The endpoint returns HTTP 402 with a valid x402 challenge on POST, confirming it is live.https://lowpaymentfee.com/api/v1/ehr/93
- —Payment is 20,000 base units of USDC (USD Coin) on the Base network, equaling $0.02.https://lowpaymentfee.com/api/v1/ehr/93
- —The platform advertises $0.02 per request, no API keys, no rate limits, and instant access.https://lowpaymentfee.com
- —Documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no substantive content.https://lowpaymentfee.com/docs