x402-gated EHR endpoint on Base, pay $0.02 per request in USDC with no API keys.
What it does
This endpoint at `/api/v1/ehr/74` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific `/ehr/74` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document this particular endpoint. The platform advertises a flat $0.02 per request pricing model across all endpoints.
Payment is handled via the x402 protocol on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The probe confirms the endpoint is live, returning a 402 challenge with `maxAmountRequired` of 20000 base units, which equals $0.02 (USDC uses 6 decimals). The endpoint accepts POST requests and returns `application/json`. No API keys, rate limits, or upfront commitments are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the `/ehr/74` endpoint actually returns. The EHR designation raises potential concerns about health data regulation (HIPAA, etc.), but no information is available to assess compliance.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific resource (ID 74)
- —Integrating EHR data into agent workflows without managing API keys
- —Paying per-request for health data access using USDC on Base
Fit
Best for
- —Agents needing on-demand EHR data with crypto micropayments
- —Developers prototyping health data integrations without subscription commitments
- —x402-compatible wallets seeking low-friction API access
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation or schema validation before integration
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/74 \
-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 /api/v1/ehr/74 actually returns, no request/response schema, and no examples. The EHR path is not listed on the provider's landing page. This is effectively a stub listing.
Warnings
- —The /ehr/74 path is not listed among the provider's advertised APIs — it may be undocumented, experimental, or deprecated.
- —No request or response schema is available; callers cannot know what data to send or expect back.
- —EHR (Electronic Health Record) data may be subject to HIPAA or other health data regulations — no compliance information is provided.
- —All documentation pages (docs, API, pricing, README) returned only a 'Connect wallet' prompt with no content.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/74
- —Platform advertises $0.02 per request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/74