Pay-per-call medical records API on Base, settled in USDC via x402.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 25) via the x402 payment protocol. Each request is a POST that costs up to $0.02 in USDC on the Base network. No API keys or rate limits are required; callers simply attach an x402 payment header to access the resource.
The provider site (lowpaymentfee.com) hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request and settled on Base in USDC. This specific endpoint falls under a "medical/records" path, but no documentation, OpenAPI schema, or example responses are available to clarify what data is returned beyond the stated MIME type of application/json.
Because the endpoint deals with medical records, consumers should exercise caution regarding data provenance, accuracy, and regulatory compliance (e.g., HIPAA in the US). The lack of documentation makes it impossible to verify what fields are returned, whether the data is synthetic or real, or what input parameters the POST body expects.
Capabilities
Use cases
- —Retrieving medical record data for record ID 25 via a single paid API call
- —Integrating pay-per-use health data into agent workflows without API key management
- —Programmatic access to structured medical record JSON
Fit
Best for
- —Agents needing on-demand medical record lookups with crypto micropayments
- —Developers exploring x402 payment-gated health data APIs
- —Prototyping workflows that consume medical data without subscription commitments
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of large medical datasets (single-record endpoint, pay-per-call)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/25 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no documentation, no example request/response, and the medical records domain raises regulatory concerns with zero transparency about data provenance.
Warnings
- —No documentation or OpenAPI schema available — request body format and response fields are unknown.
- —Endpoint serves 'medical records' data with no information about data provenance, accuracy, or regulatory compliance.
- —Potential HIPAA / health-data regulatory concerns — no compliance disclosures found.
- —The /api, /pricing, and /README pages all returned only a 'Connect wallet' prompt with no useful content.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/medical/records/25
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/25