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/15` 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 at path `/ehr/15` is labeled "Premium API Access" but its exact data payload is unclear — the path prefix "ehr" suggests Electronic Health Records, and "15" may be a record or resource identifier. However, no documentation, schema, or sample response is available to confirm what data is returned.
The endpoint is live and responds with a valid x402 challenge (HTTP 402) requiring payment of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the platform's uniform pricing across all endpoints. Payment is made via the x402 "exact" scheme, with a 300-second timeout. No API keys, accounts, or rate limits are advertised — callers simply attach an X-PAYMENT header with a valid payment proof.
The broader lowpaymentfee.com platform offers endpoints across data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/crypto (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). All share the same $0.02/request pricing and x402 payment flow. Documentation pages exist but returned only a "Connect wallet" prompt with no substantive content during crawl, so the actual request/response schemas for this and other endpoints remain unknown.
Capabilities
Use cases
- —Retrieving health record data (EHR) on a per-request payment basis
- —Agent-driven data access without pre-registration or API keys
- —Programmatic access to premium data behind crypto micropayments
Fit
Best for
- —Agents or services that need on-demand EHR data without account setup
- —Developers experimenting with x402 pay-per-call protocols
- —Low-volume consumers who prefer pay-as-you-go over subscriptions
Not for
- —Production healthcare applications requiring HIPAA-compliant, well-documented APIs
- —High-volume bulk data retrieval where per-request pricing is inefficient
- —Users who need detailed API documentation and response schemas before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/15 \
-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 the /ehr/15 resource actually returns. No request or response schema, no examples, and all doc pages returned only 'Connect wallet'. The 'EHR' label is unverified and the endpoint is effectively a stub listing.
Warnings
- —No documentation available — all doc pages returned only 'Connect wallet' with no content
- —The meaning of '/ehr/15' is unclear; 'EHR' may imply health data which could be a regulated category (HIPAA)
- —No request body schema or response schema is provided anywhere
- —No OpenAPI spec or AI plugin manifest found
- —Cannot verify what data is actually returned without making a paid request
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/15
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/15
- —Documentation pages returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs