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 33) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) 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, crypto, and utility services—all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This specific endpoint sits under the `/api/v1/medical/records/` path, but the site's landing page does not list medical endpoints among its advertised categories, so the exact data returned and the input schema are unknown.
Because there is no OpenAPI spec, no documentation beyond the landing page, and no example request/response for this medical records endpoint, the actual payload structure must be discovered by calling the endpoint with a valid x402 payment header. The endpoint is confirmed live (returns a proper 402 challenge). Agents should be aware this endpoint deals with medical data, which may carry regulatory implications (HIPAA, GDPR, etc.).
Capabilities
Use cases
- —Retrieving medical record data for record ID 33 via a single paid POST request
- —Integrating pay-per-call health data access into agent workflows
- —Programmatic access to medical records without subscription or API key management
Fit
Best for
- —Agents needing on-demand medical record lookups with no subscription
- —Developers exploring x402 micropayment-gated health data APIs
- —Workflows requiring keyless, pay-as-you-go access to structured medical data
Not for
- —Bulk retrieval of large medical datasets (no batch endpoint documented)
- —Use cases requiring HIPAA-compliant audit trails (compliance status unknown)
- —Users who need detailed API documentation or schema guarantees before calling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/33 \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"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 for the medical records path, and the landing page does not even list medical endpoints. The data content and input format are entirely unknown. Additionally, medical data raises regulatory concerns that are unaddressed.
Warnings
- —No OpenAPI or schema documentation available for this endpoint.
- —The /api/v1/medical/records/ path is not listed among the provider's advertised API categories—its legitimacy and data content are unverified.
- —Medical/health data may be subject to HIPAA, GDPR, or other regulations; the provider's compliance posture is unknown.
- —No example request or response bodies are available; input schema must be discovered empirically.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired 20000.https://lowpaymentfee.com/api/v1/medical/records/33
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/33