x402-gated EHR endpoint on Base, pay $0.02 per request in USDC — no API keys required.
What it does
This endpoint at `/api/v1/ehr/27` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs settled in USDC on the Base network. The specific resource at path `/ehr/27` is listed under the generic title "Premium API Access" with no further documentation about what data it returns. The "ehr" path segment suggests Electronic Health Records, but no schema, sample response, or documentation is provided to confirm the payload contents.
The endpoint is live and returns a valid x402 challenge (HTTP 402) requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The platform advertises no API keys, no rate limits, and instant access across all its endpoints. The accepted HTTP method is POST and the response MIME type is application/json.
Beyond the x402 challenge metadata, documentation is essentially absent — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no explanation of what the `/ehr/27` resource actually provides. Prospective callers should treat this as an opaque JSON endpoint until the provider publishes proper documentation.
Capabilities
Use cases
- —Retrieving health-related data records on a per-call payment basis
- —Integrating EHR data into agent workflows without managing API keys
- —Testing x402 micropayment flows against a live endpoint
Fit
Best for
- —Developers exploring x402 pay-per-call patterns on Base
- —Agents needing keyless, on-demand access to a JSON data endpoint
- —Prototyping micropayment-gated API integrations
Not for
- —Production healthcare applications requiring HIPAA-compliant, well-documented EHR APIs
- —Use cases needing detailed request/response schemas before integration
- —Bulk data retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/27 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation: no OpenAPI spec, no request/response schema, no description of what 'ehr/27' actually returns. The docs pages are empty. The 'EHR' path is suggestive but unconfirmed, making this effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
- —The 'ehr' path segment suggests Electronic Health Records but this is unconfirmed; actual response payload is unknown.
- —No request body schema or response schema is published; callers cannot know what to send or expect back.
- —If this truly serves health data, regulatory compliance (HIPAA, etc.) is entirely unaddressed in available materials.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/27
- —The platform advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/27
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs