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/5`) using the x402 payment protocol. It is live and returns a 402 challenge requiring payment in USDC on the Base network. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD. Payment is made via the "exact" scheme to the specified wallet address, and the endpoint accepts HTTP POST requests.
The provider's landing page lists a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, infrastructure utilities, and more — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here is under a "medical/records" path, which is not explicitly mentioned on the landing page's catalog. No OpenAPI schema, request/response examples, or detailed documentation were found for this endpoint. The response MIME type is advertised as `application/json`.
Because this endpoint deals with medical records, consumers should exercise caution regarding data authenticity, regulatory compliance (e.g., HIPAA), and the provenance of the data returned. No documentation exists to clarify what data is actually served, whether it is synthetic/demo data, or what the expected request body should contain.
Capabilities
Use cases
- —Retrieving medical record data for a specific record ID via a single paid API call
- —Integrating health data into agent workflows that support x402 micropayments
- —Prototyping pay-per-use medical data access without API key registration
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents that can autonomously settle USDC payments on Base
- —Quick access to a medical records endpoint without subscription or signup
Not for
- —Production healthcare applications requiring HIPAA-compliant, auditable data pipelines
- —Use cases needing detailed API documentation, request schemas, or SLAs
- —Bulk retrieval of large medical datasets (pay-per-call model may be costly at scale)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/5 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation for this specific medical records path, and the endpoint is not listed in the provider's own catalog. The medical/health category raises regulatory concerns with zero documentation.
Warnings
- —No documentation or schema available for the /api/v1/medical/records/5 endpoint
- —This endpoint path is not listed on the provider's landing page catalog — its actual behavior is unknown
- —Medical records data may be subject to HIPAA or other health data regulations; no compliance information is provided
- —No request body schema or response examples are available; the actual data returned is entirely unknown
- —Could be synthetic/demo data — no provenance or authenticity guarantees
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/5
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/5
- —The landing page lists APIs in categories: Data & Analytics, AI & ML, Finance & Web3, Infrastructure — but does not list medical/recordshttps://lowpaymentfee.com