x402-gated premium API endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at `/api/v1/ehr/76` is part of the lowpaymentfee.com platform, which offers 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/76` path is listed as "Premium API Access" but its exact functionality is not documented on the site — the "ehr" prefix may suggest electronic health records or a similar domain, but 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`). The `maxAmountRequired` is 20,000 base units, which at 6 decimals equals $0.02 per request. The platform advertises a flat $0.02/request pricing model across all endpoints with no API keys, no rate limits, and no minimum commitments. The x402 scheme used is "exact" with a 300-second payment timeout.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no description of what data this endpoint returns or what input it expects. The `outputSchema` in the x402 challenge indicates it accepts HTTP POST requests and is discoverable, but provides no field-level detail. Prospective users should be aware that without documentation, the actual behavior of this endpoint is unknown.
Capabilities
Use cases
- —Accessing premium data behind a per-request micropayment wall
- —Agent-driven API consumption without API key management
- —Programmatic pay-as-you-go data retrieval on Base
Fit
Best for
- —Developers wanting zero-signup, pay-per-call API access
- —AI agents that can settle x402 payments autonomously
- —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 a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/ehr/76 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what /api/v1/ehr/76 actually does, what inputs it expects, or what it returns. No OpenAPI spec, no examples, and the docs pages are empty. The listing is effectively a stub.
Warnings
- —The exact purpose and data returned by /api/v1/ehr/76 are completely undocumented.
- —The 'ehr' path segment may imply health data, which could fall under regulated categories (HIPAA, etc.) — exercise caution.
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
- —No request or response schema is available; integration requires trial-and-error or contacting the provider.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/ehr/76
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/ehr/76
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs