x402-gated premium API endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at `/api/v1/ehr/84` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific `/api/v1/ehr/84` path is listed under the title "Premium API Access" but its exact functionality is not documented on the site — the "ehr" path segment suggests it may relate to Electronic Health Records or a similar domain, though this is unconfirmed. The endpoint is live and returns a valid x402 challenge.
Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 "exact" scheme. The `maxAmountRequired` is 20,000 base units, which at 6 decimals for USDC equals $0.02 per request — consistent with the site's advertised flat $0.02/request pricing across all endpoints. No API keys are required; access is granted by attaching an X-PAYMENT header with a valid payment proof. The endpoint accepts POST requests and returns `application/json`.
The broader lowpaymentfee.com platform advertises no rate limits, no minimums, and instant access. However, documentation is extremely sparse — 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 description of what data `/api/v1/ehr/84` actually returns. Without knowing the input parameters or output format, integrating this endpoint requires experimentation or direct contact with the provider.
Capabilities
Use cases
- —Accessing premium data behind a per-request USDC paywall
- —Agent-driven API consumption without pre-registration or API keys
- —Programmatic retrieval of EHR-related data (if confirmed)
Fit
Best for
- —Developers wanting zero-signup, pay-as-you-go API access
- —AI agents with x402-compatible payment capabilities
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Anyone needing documented request/response schemas before integration
- —Use cases requiring guaranteed SLAs or support contracts
- —Users without Base-network USDC wallets
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/84 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what /api/v1/ehr/84 actually does, what inputs it expects, or what it returns. No OpenAPI spec, no examples, and all doc pages are empty. The 'ehr' path is unexplained. This is effectively a stub listing.
Warnings
- —The exact purpose and data returned by /api/v1/ehr/84 are completely undocumented.
- —The 'ehr' path segment may relate to Electronic Health Records, which could involve regulated/sensitive data — exercise caution.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content.
- —No request or response schema is available; integration requires trial and error.
Citations
- —The site advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network.https://lowpaymentfee.com/api/v1/ehr/84
- —Documentation pages render only a 'Connect wallet' prompt with no substantive content.https://lowpaymentfee.com/docs