Pay-per-call medical records API on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/12`) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge. The maximum amount required per call is 20,000 base units of USDC, which at 6 decimals equals $0.02 per request.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. The specific endpoint being listed here is in the medical records category, which is not prominently featured on the provider's landing page but is live and returning a valid 402 challenge.
No OpenAPI schema, request/response examples, or detailed documentation were found for this endpoint. The crawled pages beyond the homepage returned only a "Connect wallet" prompt with no additional content. The exact structure of the POST body and the response payload are unknown. Because this endpoint deals with medical records, it may involve sensitive or regulated health data — consumers should exercise caution and verify compliance requirements.
Capabilities
Use cases
- —Retrieving medical record data for a specific record ID via a single paid API call
- —Integrating health data lookups into agent workflows that can settle payments on Base
- —Accessing structured medical information without API key registration
Fit
Best for
- —Agents or applications that need on-demand medical record access with crypto micropayments
- —Developers prototyping health data integrations without signup friction
- —x402-compatible clients on the Base network
Not for
- —Production healthcare applications requiring HIPAA or regulatory compliance guarantees (no compliance documentation found)
- —Users who need bulk or batch medical record retrieval (pay-per-call model)
- —Consumers without USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/12 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no request/response documentation, no examples, and the crawled pages are nearly empty. The medical records category is not listed on the provider's homepage, and the nature of the data returned is entirely unknown. The regulated health-data domain further reduces confidence.
Warnings
- —No request or response schema documented — input/output structure is unknown
- —Medical records endpoint may involve regulated health data (e.g., HIPAA); no compliance or privacy documentation found
- —This specific endpoint path (/api/v1/medical/records/12) is not listed on the provider's public API catalog
- —Crawled documentation pages returned no useful content beyond 'Connect wallet'
Citations
- —The endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/12
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/12