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/83` 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/83` is labeled "Premium API Access" but its exact functionality is unclear — the path segment "ehr" may suggest Electronic Health Records or a similar domain, but no documentation or schema describes the request/response format for this particular endpoint.
The endpoint is live and returns a valid x402 challenge over the Base network. Payment is settled in USDC (contract `0x8335…2913`) with a maximum amount of 20,000 base units, which at 6 decimals equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all endpoints, no API keys, no rate limits, and instant access. The x402 challenge specifies the POST method and a 300-second payment timeout.
Documentation is extremely sparse. 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 example payloads available for this or any other endpoint on the platform. The actual data returned by `/api/v1/ehr/83` cannot be determined from the available material.
Capabilities
Use cases
- —Accessing health-related or premium data records via a single paid API call
- —Agent-driven workflows that need keyless, pay-per-request data access on Base
- —Programmatic retrieval of record ID 83 from the EHR endpoint
Fit
Best for
- —Developers wanting zero-signup, pay-as-you-go API access
- —AI agents with x402-compatible wallets on Base
- —Use cases requiring small per-call payments without subscriptions
Not for
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Bulk data retrieval where per-request pricing would be cost-prohibitive
- —Anyone needing clarity on what data the endpoint actually returns before paying
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/83 \
-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 on what the /ehr/83 resource actually returns. No OpenAPI spec, no request/response schema, no examples. The "EHR" path is ambiguous and undocumented. This is effectively a stub listing.
Warnings
- —The endpoint path '/api/v1/ehr/83' is not listed among the advertised APIs on the landing page — it may be an unlisted or experimental resource.
- —No documentation exists for this endpoint: no schema, no examples, no description of what data is returned.
- —The 'ehr' path segment suggests possible health/medical data, which may fall under regulated categories (HIPAA, etc.) — no compliance information is provided.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no substantive content.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/ehr/83
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/83
- —Platform advertises $0.02/request pricing, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —The /api/v1/ehr/83 path is not listed among the advertised endpoints on the landing pagehttps://lowpaymentfee.com