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/55` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs settled in USDC on the Base network. The specific resource at path `/ehr/55` is labeled "Premium API Access" in the x402 challenge, but its exact data payload is undocumented — the path prefix "ehr" suggests Electronic Health Records, though no schema or sample response is provided by the provider.
The endpoint is live and returns a standard x402 challenge (HTTP 402) requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is made via the `exact` scheme with a 300-second timeout. No API key or account registration is needed; callers attach an `X-PAYMENT` header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all priced at $0.02 per request. However, the `/api/v1/ehr/55` path is not listed on the provider's landing page among the advertised APIs, and no documentation, input schema, or response schema is available for this specific endpoint. The docs, pricing, and README pages all resolve to a minimal "Connect wallet" stub with no additional content.
Capabilities
Use cases
- —Retrieving health record data (EHR) via a single paid request
- —Agent-driven data access without pre-registration or API keys
- —Programmatic pay-per-call access to premium data on Base L2
Fit
Best for
- —AI agents needing on-demand data access with crypto micropayments
- —Developers who want keyless, pay-as-you-go API access
- —Applications already integrated with x402 payment protocol on Base
Not for
- —Users who need documented schemas and guaranteed SLAs before integrating
- —HIPAA-regulated workflows requiring compliance guarantees
- —High-volume batch processing where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/55 \
-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 what /api/v1/ehr/55 actually returns. No input schema, output schema, example responses, or docs pages with real content exist. The EHR path is not even listed among the provider's advertised APIs. This is effectively a stub listing.
Warnings
- —The /api/v1/ehr/55 path is NOT listed among the provider's advertised endpoints — it may be a test, placeholder, or unlisted resource.
- —No input or output schema is documented; the actual response payload is unknown.
- —The 'ehr' path prefix suggests health data, which may be subject to HIPAA or other regulatory requirements — no compliance information is provided.
- —All documentation pages (/docs, /pricing, /README, /api) return only a 'Connect wallet' stub with no usable content.
- —The provider's landing page lists many API categories but none match this specific endpoint path.
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/55
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/55
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The /api/v1/ehr/55 path is not listed among the provider's advertised API endpointshttps://lowpaymentfee.com
- —Documentation pages resolve to minimal 'Connect wallet' stubshttps://lowpaymentfee.com/docs