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 (record ID 63) 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 an exact-scheme challenge requiring up to 20,000 base units (i.e., $0.02 per request, since USDC uses 6 decimals).
The provider site 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 commitments. This specific endpoint falls under a "medical records" path, but the site's landing page does not list it among its advertised categories, and no documentation, schema, or sample payloads are available for this particular resource.
Because no request or response schema is documented beyond the x402 challenge metadata, callers should expect to experiment with POST body formats. The endpoint is confirmed live (returns a proper 402 x402 challenge). However, the medical-records domain raises regulatory and sensitivity concerns — there is no visible information about HIPAA compliance, data provenance, or what data is actually returned.
Capabilities
Use cases
- —Retrieving medical record data for record ID 63 via a single paid API call
- —Integrating pay-per-call health data into agent workflows without API key management
- —Programmatic access to medical records settled in USDC on Base
Fit
Best for
- —Developers exploring x402 pay-per-call patterns with health data
- —Agents needing keyless, on-demand medical record retrieval
- —Prototyping crypto-settled healthcare data pipelines
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data sources
- —Bulk retrieval of many medical records (single record ID only, no documented batch support)
- —Users who need detailed API documentation or response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/63 \
-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/response schemas, no OpenAPI spec, and the medical records path is not listed on the provider's own landing page. The regulated nature of medical data with no compliance information further lowers confidence.
Warnings
- —Medical/health data endpoint with no visible HIPAA compliance or data provenance information
- —This specific endpoint (/api/v1/medical/records/63) is not listed among the provider's advertised APIs on the landing page
- —No request body schema or response schema documented — callers must guess the POST format
- —Regulated data category: exercise caution before relying on this for any real health data use case
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/63
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/63