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 access to an Electronic Health Record (EHR) resource via the x402 payment protocol. The specific endpoint `/api/v1/ehr/1` is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 micropayments on the Base network using USDC.
The x402 challenge confirms the endpoint is live and accepts POST requests. Payment settles on Base using the USDC contract (0x8335…2913) with an exact-scheme payment of 20,000 base units, which equals $0.02 (USDC has 6 decimals). The platform advertises a flat $0.02 per request across all endpoints, with no API keys, no rate limits, and no minimum commitments. The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no request/response examples, and no description of what the EHR endpoint actually returns or what input it expects. The endpoint is discoverable and accepts HTTP POST, but beyond that the data model is unknown. The listing title "Premium API Access" is generic and does not clarify the EHR use case. Prospective callers should expect to experiment or contact the provider for documentation.
Capabilities
Use cases
- —Retrieving electronic health record data for a specific record ID
- —Integrating EHR lookups into agent workflows that support x402 payments
- —Accessing health data without traditional API key provisioning
Fit
Best for
- —Developers or agents needing on-demand EHR data with crypto micropayments
- —Prototyping health data integrations without signup or API key management
- —x402-compatible agents on the Base network
Not for
- —Production healthcare applications requiring HIPAA-compliant, well-documented APIs
- —Users who need detailed schema documentation or guaranteed SLAs
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/1 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request format, response schema, or what EHR data is actually served. No OpenAPI spec, no examples, and all doc pages are empty wallet-connect stubs. The EHR endpoint itself is not even listed on the provider's homepage, raising questions about its status.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages are all empty beyond a wallet connect prompt.
- —The /api/v1/ehr/1 endpoint is not listed among the provider's advertised APIs on the homepage, so its availability and data content are uncertain.
- —No request or response schema is provided; callers must guess at the expected input format.
- —EHR data may be subject to healthcare regulations (e.g., HIPAA); no compliance information is provided.
- —Unknown whether this returns real or synthetic health data.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/1
- —USDC contract address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/1
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The /docs, /pricing, /api, and /README pages render only a Connect wallet prompt with no documentationhttps://lowpaymentfee.com/docs