x402-gated EHR endpoint on Base, pay $0.02 per request in USDC — no API keys required.
What it does
This endpoint at lowpaymentfee.com provides premium API access to an EHR (Electronic Health Record) resource at path `/api/v1/ehr/66`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated via the x402 payment protocol on the Base network.
The endpoint accepts POST requests 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). The x402 challenge is version 1 with the "exact" payment scheme and a 300-second timeout. No API keys, subscriptions, or rate limits are advertised; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The landing page lists available endpoints and pricing, but the `/docs`, `/pricing`, `/api`, and `/README` pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what the `/api/v1/ehr/66` endpoint actually returns or what input it expects. The "EHR" label suggests electronic health records, but no details about the data source, format, or compliance posture are provided. Prospective users should exercise caution given the healthcare-adjacent naming and total lack of documentation.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 66)
- —Programmatic access to health data without subscription or API key management
- —Agent-driven healthcare data retrieval with per-call crypto micropayments
Fit
Best for
- —Developers needing on-demand EHR data access without signup
- —AI agents that can settle x402 payments on Base in USDC
- —Prototyping health data integrations with minimal commitment
Not for
- —Production healthcare systems requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation or schema guarantees before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/66 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is zero documentation on request format, response schema, or what data the EHR endpoint actually provides. No OpenAPI spec exists, and all doc pages render only 'Connect wallet'. The healthcare-adjacent naming with no compliance information is a significant concern.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
- —No OpenAPI or request/response schema provided; input format is unknown
- —Endpoint labeled 'EHR' (Electronic Health Record) with no information about data provenance, accuracy, or regulatory compliance (e.g., HIPAA)
- —The specific resource ID '66' is opaque — unclear what entity or record it refers to
- —Healthcare data endpoints may be subject to regulatory requirements not addressed by the provider
Citations
- —The endpoint returns a 402 challenge with x402 version 1, exact scheme, on Base network, with maxAmountRequired of 20000 in USDChttps://lowpaymentfee.com/api/v1/ehr/66
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/66
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs