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 medical record data (record ID 50) 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 cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
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 minimum commitments. This specific endpoint falls under a "medical/records" path, but the provider's landing page does not list it among its advertised categories, and no documentation, schema details, or sample responses are available for this particular resource.
Because the endpoint is in a medical/health data category and no documentation describes what data is returned, callers should exercise caution. There is no OpenAPI spec, no request/response schema beyond the x402 challenge metadata, and no explanation of what "record 50" contains or what POST body is expected. The endpoint is confirmed live (returns 402 challenge correctly), but the lack of documentation significantly limits confidence in its utility.
Capabilities
Use cases
- —Retrieving medical record data for record ID 50 via a single paid API call
- —Integrating health data into agent workflows that support x402 micropayments
- —Programmatic access to medical records without API key registration
Fit
Best for
- —Agents or applications that support x402 payment protocol on Base
- —Use cases requiring on-demand, keyless access to medical record data
- —Developers experimenting with x402 micropayment-gated APIs
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Bulk retrieval of many medical records (only record 50 is addressed by this endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/50 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request format, response schema, or what medical data is returned. The endpoint path (medical/records) is not listed on the provider's own landing page. This is effectively a stub listing with significant unknowns, especially concerning given the medical data category.
Warnings
- —Medical/health data endpoint with no documentation on data contents, provenance, or compliance (e.g., HIPAA).
- —This endpoint path is not listed among the provider's advertised APIs on the landing page.
- —No OpenAPI spec, request schema, or response schema available.
- —No information on what POST body is expected or what 'record 50' represents.
- —Regulated data category (medical records) — verify legal and compliance requirements before use.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/medical/records/50
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The medical/records endpoint is not listed among the provider's advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure).https://lowpaymentfee.com