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/3`) using the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network in USDC (contract 0x8335…2913) using the "exact" scheme, with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).
The provider lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all advertised at $0.02 per request with no API keys, no rate limits, and no minimum commitments. The specific endpoint listed here falls under a "medical records" path, though no detailed documentation, request schema, or response schema is available beyond the x402 challenge metadata. The endpoint is live and returns a proper 402 challenge.
Because no OpenAPI spec, request body schema, or example responses were found, the actual data returned and the required POST body are unknown. The "medical/records" path suggests health-related data, which may carry regulatory implications (HIPAA, etc.). Users should exercise caution and verify compliance requirements before integrating.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without API key management
- —Programmatic access to medical records with crypto micropayments
Fit
Best for
- —Agents or apps needing on-demand medical record lookups with no subscription
- —Developers wanting frictionless pay-per-call access on Base L2
- —Crypto-native workflows that settle in USDC
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Use cases needing bulk or batch medical data retrieval at scale
- —Users who need detailed API documentation and guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/3 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond the landing page listing, and the medical records path has no further explanation. The actual data content and required inputs are entirely unknown.
Warnings
- —No request or response schema available — POST body format is unknown
- —Medical/health data endpoint may be subject to HIPAA or other healthcare regulations; no compliance information provided
- —No documentation beyond the homepage listing; endpoint behavior must be discovered empirically
- —The specific record ID '3' in the path is hardcoded — unclear if other IDs are available or how to discover them
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, Base network, USDC asset, maxAmountRequired 20000https://lowpaymentfee.com/api/v1/medical/records/3
- —The provider advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/medical/records/3