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/6`) using the x402 payment protocol. It is one of many endpoints offered by the lowpaymentfee.com platform, which hosts a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. All endpoints on the platform share a uniform pricing model of $0.02 per request, paid in USDC on the Base network with no API keys, rate limits, or commitments required.
The specific endpoint probed returns an x402 challenge (HTTP 402) confirming it is live. The challenge specifies an "exact" payment scheme on the Base network, with a `maxAmountRequired` of 20,000 base units of USDC (the asset at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). Since USDC uses 6 decimals, this translates to $0.02 per call. The endpoint accepts POST requests and returns `application/json`.
Important caveats: there is no OpenAPI schema, no documentation of request parameters or response structure, and no examples available for this specific medical records endpoint. The platform's landing page lists this endpoint's category implicitly (it is not listed among the publicly advertised APIs on the homepage), so its exact functionality, required input fields, and response format are unknown. The "medical records" path suggests health-related data, which may carry regulatory implications (e.g., HIPAA). Users should exercise caution and verify compliance requirements before integrating.
Capabilities
Use cases
- —Retrieving medical record data for record ID 6 via a single paid API call
- —Integrating health data into agent workflows that support x402 micropayments
- —Accessing structured medical information without API key registration
Fit
Best for
- —Agents or applications that can settle x402 payments in USDC on Base
- —Developers wanting frictionless pay-per-call access to medical data without signup
- —Prototyping health data integrations with minimal commitment
Not for
- —Production healthcare applications requiring HIPAA-compliant audit trails and data handling guarantees
- —Use cases needing detailed API documentation, schemas, or SLAs
- —Bulk retrieval of many medical records (no batch endpoint documented)
Quick start
# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Without payment infrastructure, you'll receive a 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/6
# Returns 402 with x402 payment challenge (USDC on Base, $0.02)Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation of request/response schemas, no OpenAPI spec, no examples, and the medical records endpoint is not even listed on the provider's public homepage. The health/medical category raises regulatory concerns with zero compliance information available.
Warnings
- —No API documentation, OpenAPI schema, or request/response examples available for this endpoint
- —This endpoint path suggests medical/health data — regulatory compliance (HIPAA, GDPR) is unverified and undocumented
- —The /api/v1/medical/records/6 path is not listed among the provider's publicly advertised APIs on the homepage
- —The hardcoded record ID '6' in the path suggests this may be a single fixed resource rather than a general-purpose query endpoint
Citations
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/6
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —The endpoint accepts POST method and returns application/json as specified in the x402 outputSchemahttps://lowpaymentfee.com/api/v1/medical/records/6