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/37` is part of the lowpaymentfee.com platform, which offers a variety of pay-per-call APIs gated via the x402 protocol on the Base network. The specific resource at path `/ehr/37` is labeled "Premium API Access" and returns JSON. Payment is settled in USDC (contract `0x8335…2913` on Base) at a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys, subscriptions, or rate limits are advertised — callers simply attach an x402 payment header to each POST request.
The broader lowpaymentfee.com platform lists endpoints across data & analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation), all at the same $0.02/request price point. However, the specific `/api/v1/ehr/37` path suggests an Electronic Health Record (EHR) resource, which is not documented on the site's landing page among the listed API categories. No schema, field definitions, or example responses are provided for this endpoint, so the exact data returned is unknown.
The endpoint is confirmed live: it returns a proper x402 version-1 challenge with a 402 status code when called without payment. The x402 challenge specifies the `exact` payment scheme, a 300-second timeout, and the payTo address `0x1A2B…85F3`.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-request payment basis
- —Integrating EHR data into agent workflows without managing API keys or subscriptions
- —Accessing health data from an x402-compatible agent or wallet
Fit
Best for
- —Agents or applications that need on-demand EHR data with micropayments
- —Developers prototyping health-data integrations without upfront commitments
- —x402-native wallets and autonomous agents on Base
Not for
- —Bulk or high-volume EHR data pipelines where per-request pricing is inefficient
- —Use cases requiring detailed schema documentation or SLA guarantees before integration
- —Applications that cannot settle payments in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/37 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no request/response schema, and the /ehr/37 path is not listed among the site's advertised APIs, making the actual data returned entirely unknown. The crawled docs/pricing/API pages are empty beyond a wallet-connect prompt.
Warnings
- —The /api/v1/ehr/37 path is not listed among the provider's publicly documented endpoints — its purpose and data schema are unknown.
- —No request body schema or response schema is available; callers cannot know what fields to send or expect.
- —EHR data may be subject to healthcare regulations (HIPAA, GDPR) — no compliance information is provided.
- —Documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no useful content.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/37
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/37
- —Platform advertises $0.02/request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —The /api/v1/ehr/37 path is not among the endpoints listed on the landing pagehttps://lowpaymentfee.com