Pay-per-call medical records API on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/4`) 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 a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
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. This specific endpoint falls under a "medical records" path, but the provider's landing page does not document the medical records endpoints in its public catalog, nor does it describe the request body schema or the shape of the response. The endpoint is live and returns a well-formed 402 challenge, confirming it is operational.
Because there is no OpenAPI spec, no request/response schema documentation, and no description of what medical data is returned or what input the POST body expects, this listing carries significant uncertainty. Callers should experiment with the endpoint or contact the provider for integration details. The medical records domain also raises regulatory considerations (e.g., HIPAA in the US).
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without API key provisioning
- —Programmatic access to structured medical information settled via crypto micropayments
Fit
Best for
- —Agents or applications that need on-demand medical record lookups
- —Developers wanting keyless, pay-per-use health data access
- —Crypto-native workflows on the Base L2 network
Not for
- —Production healthcare systems requiring HIPAA-compliant audit trails and BAAs
- —Use cases needing bulk or batch medical data retrieval at scale
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/4 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no documented request/response schema, and the medical records path is not listed on the provider's own landing page. The medical/health domain raises regulatory flags. Effectively a stub listing.
Warnings
- —No request body schema or response schema documented — callers must guess the POST payload
- —Medical records endpoint is not listed in the provider's public API catalog, raising questions about its intended audience
- —Medical/health data may be subject to HIPAA or other health-data regulations; no compliance information is provided
- —No OpenAPI spec or detailed documentation available from the provider
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/4
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/4
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The medical records endpoint is not listed among the provider's publicly cataloged APIshttps://lowpaymentfee.com