Pay-per-call medical records endpoint 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/68`) 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 a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are advertised; access is gated purely by the x402 micropayment challenge.
The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request. This specific endpoint sits under the medical records path, though the crawled material does not document the request body schema, response fields, or the nature of the medical data returned. The x402 challenge confirms the endpoint is live (HTTP 402 returned with a valid payment challenge), and the root site loads successfully.
Because the endpoint deals with medical records, consumers should be aware of potential regulatory considerations (e.g., HIPAA in the US, GDPR in the EU). The lack of documentation about what data is returned, how it is sourced, and what privacy safeguards are in place is a significant gap. There is no OpenAPI spec, no example request/response, and no detailed documentation available from the crawl.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without subscription commitments
- —Programmatic access to medical records for research or analytics pipelines
Fit
Best for
- —Agents needing on-demand medical record lookups without API key management
- —Developers prototyping health data integrations with minimal setup
- —Low-volume consumers who prefer pay-per-use over subscriptions
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —High-volume bulk medical data retrieval where per-call pricing is inefficient
- —Use cases requiring detailed schema documentation and SLA guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/68 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (valid x402 402 challenge captured), but there is no documentation of request/response schemas, no OpenAPI spec, and no crawled content beyond a generic landing page. The medical records domain raises regulatory concerns that are entirely unaddressed. Effectively a stub listing.
Warnings
- —No request body schema or response schema documented — consumers cannot know what to send or what they will receive.
- —Endpoint serves medical records — potential HIPAA, GDPR, and other health-data regulatory requirements are not addressed anywhere in the crawled material.
- —No OpenAPI specification, no examples, and no detailed documentation available.
- —The nature and source of the medical data is completely unknown.
Citations
- —Endpoint returns HTTP 402 with x402 challenge advertising USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/68
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/68