x402-gated EHR data endpoint on Base, pay $0.02 per request in USDC — no API keys required.
What it does
This endpoint at lowpaymentfee.com provides access to an Electronic Health Record (EHR) resource via the x402 payment protocol. The specific path `/api/v1/ehr/42` suggests retrieval of a particular EHR record (ID 42). Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum amount of 20,000 base units, which equals $0.02 given USDC's 6 decimals. The endpoint accepts POST requests and returns application/json.
The broader lowpaymentfee.com platform hosts a variety of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /README) all resolve to a minimal "Connect wallet" prompt with no substantive technical documentation, OpenAPI spec, or example payloads available.
Because the specific EHR endpoint lacks any schema documentation, request/response examples, or explanation of what data it returns, agents should treat this as a low-documentation endpoint. The "EHR" label implies health-related data, which may carry regulatory considerations (HIPAA, etc.). The x402 challenge is live and well-formed, confirming the endpoint is operational.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific patient or record ID
- —Integrating EHR data into health-tech agent workflows with per-request micropayments
- —Accessing health data without managing API keys or subscriptions
Fit
Best for
- —Agents needing on-demand EHR data access via crypto micropayments
- —Developers prototyping health data integrations without subscription commitments
- —x402-compatible wallets and agent frameworks on Base
Not for
- —Production healthcare systems requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation or schema guarantees before integration
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/42 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint is operational and pricing is clear ($0.02 USDC on Base). However, there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and all doc pages return only a 'Connect wallet' stub. The EHR domain label raises regulatory concerns with no clarification provided.
Warnings
- —No API documentation, OpenAPI spec, or request/response examples available — all doc pages return only 'Connect wallet'
- —EHR (Electronic Health Record) data may be subject to HIPAA or other health data regulations; no compliance information is provided
- —The specific data returned by /api/v1/ehr/42 is completely undocumented — it is unclear whether this is real patient data, synthetic/demo data, or a placeholder
- —No input schema documented; POST body requirements are unknown
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/42
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/42
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /README) resolve to minimal 'Connect wallet' contenthttps://lowpaymentfee.com/docs