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/32` 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/32` is labeled "Premium API Access" but its exact data domain is unclear — the "ehr" path segment suggests Electronic Health Records, though the provider's landing page does not list or describe any EHR-specific endpoints. No documentation, request schema, or response schema is available for this particular route.
Payment is handled via the x402 protocol on the Base network. The endpoint accepts USDC (contract `0x8335…2913`) with a `maxAmountRequired` of 20,000 base units, which at 6 decimals equals $0.02 per request. This is consistent with the provider's advertised flat $0.02/request pricing across all endpoints. 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" stub with no substantive content, there is no way to confirm what data this endpoint actually returns, what POST body it expects, or whether "ehr" truly refers to health records. Prospective callers should treat this as an exploratory endpoint until the provider publishes proper documentation.
Capabilities
Use cases
- —Retrieving health record data (if EHR interpretation is correct) via a single paid POST call
- —Agent-driven data retrieval with automatic x402 micropayment settlement
- —Programmatic access to premium data without managing API keys or subscriptions
Fit
Best for
- —Developers or agents that already support x402 payment flows on Base
- —Use cases requiring keyless, pay-as-you-go API access
- —Exploratory integration where $0.02/call cost is negligible
Not for
- —Production health-data workflows requiring documented schemas, SLAs, and compliance guarantees
- —Users who need detailed API documentation or response format guarantees before integrating
- —High-volume consumers who need bulk pricing or rate-limit headroom
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/32 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>" \
-d '{}'Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/ehr/32",
"body": {},
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-proof>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation for this specific route — no request schema, no response schema, no description of what 'ehr/32' returns. The docs, pricing, and README pages are all empty stubs. The 'ehr' path is not listed anywhere on the provider's landing page, making its purpose unverifiable.
Warnings
- —The 'ehr' path segment is not listed on the provider's landing page; its actual data domain is unconfirmed.
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content.
- —No request or response schema is available — callers cannot know what POST body to send or what to expect back.
- —If 'ehr' refers to Electronic Health Records, this may involve regulated health data (HIPAA, etc.) with no visible compliance documentation.
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/ehr/32
- —maxAmountRequired is 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/ehr/32
- —Provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages /docs, /api, /pricing, /README contain only 'Connect wallet' stub contenthttps://lowpaymentfee.com/docs