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/29` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific resource at path `/ehr/29` is labeled "Premium API Access" but its exact functionality is unclear — the "ehr" path segment suggests Electronic Health Records, though no documentation confirms what data or service this endpoint actually returns.
The endpoint is live and responds with a valid x402 payment challenge. It accepts POST requests and settles on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum amount required is 20,000 base units of USDC, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing across all endpoints. Payment is made via the `exact` scheme with a 300-second timeout. No API keys or accounts are needed; access is granted purely through the x402 payment header.
Documentation is extremely sparse. The landing page lists available API categories but does not include `/api/v1/ehr/29` among them. The docs, API, pricing, 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 description of what this particular endpoint does or what parameters it accepts. Agents should treat this as a minimally documented endpoint with uncertain functionality.
Capabilities
Use cases
- —Retrieving electronic health record data (if confirmed as EHR endpoint)
- —Agent-driven pay-per-call data access without API key management
- —Programmatic access to premium data behind micropayment wall
Fit
Best for
- —Agents that can settle x402 payments in USDC on Base
- —Use cases requiring keyless, on-demand API access
- —Developers exploring x402-protocol micropayment patterns
Not for
- —Production healthcare applications requiring documented, compliant APIs
- —Users needing detailed API documentation or guaranteed SLAs
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/29 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the endpoint actually does, what request body it expects, or what it returns. The 'ehr' path is not listed among the platform's advertised APIs. No OpenAPI spec, no examples, no response schema. This is effectively a stub listing.
Warnings
- —The /api/v1/ehr/29 path is not listed among the platform's advertised endpoints — its availability and purpose are unconfirmed.
- —'EHR' typically refers to Electronic Health Records, which is a regulated data category (HIPAA in the US). No compliance or data-handling documentation is provided.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no substantive content.
- —No request or response schema is available — callers cannot know what parameters to send or what data to expect.
- —The endpoint path includes a numeric ID (29) suggesting a specific record; the semantics of this ID are undocumented.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/29
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/ehr/29
- —The /api/v1/ehr/29 path is not listed among the platform's advertised API categorieshttps://lowpaymentfee.com