Pay-per-call EHR data endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at `/api/v1/ehr/6` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol APIs spanning data analytics, AI/ML, finance, infrastructure, and apparently electronic health record (EHR) data. Each call costs $0.02 in USDC on the Base network, with no API keys, rate limits, or subscriptions required — you simply attach an x402 payment header to each request.
The specific `/api/v1/ehr/6` path suggests an endpoint that returns health-related or electronic health record data for a particular resource (ID 6). However, this endpoint is not listed on the provider's public landing page among the documented API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). No schema, field definitions, or example responses are documented for this path. The x402 challenge confirms the endpoint is live and accepts POST requests, settling payments to `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` in USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base.
Because the endpoint name implies electronic health records — a regulated data category — users should exercise caution regarding data provenance, HIPAA compliance, and whether the returned data is synthetic, anonymized, or real. No documentation clarifies this.
Capabilities
Use cases
- —Retrieving electronic health record data on a per-call payment basis
- —Integrating EHR data into agent workflows without subscription overhead
- —Testing x402 micropayment flows against a health data endpoint
Fit
Best for
- —Developers exploring x402 pay-per-call patterns
- —Agents needing on-demand health data without API key management
- —Prototyping micropayment-gated data access
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Use cases needing detailed API documentation, schemas, or SLAs
- —High-volume batch EHR data retrieval (per-call pricing adds up)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/6 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"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 /ehr/6 path — no request schema, no response schema, no examples, and the endpoint isn't even listed on the provider's own landing page. The EHR label raises regulatory concerns with no clarification provided.
Warnings
- —Endpoint /api/v1/ehr/6 is not listed among the provider's publicly documented APIs — its purpose and data content are unverified.
- —EHR (Electronic Health Record) data is a regulated category; no information is provided about HIPAA compliance, data provenance, or whether data is synthetic/anonymized.
- —No request or response schema is available; callers cannot know what fields to send or expect back.
- —Documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no substantive content.
Citations
- —The endpoint returns a 402 challenge requesting USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/ehr/6
- —Platform pricing is $0.02 per request with no API keys, rate limits, or minimumshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/6
- —The /api/v1/ehr/6 path is not listed among the provider's documented API categorieshttps://lowpaymentfee.com