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 44) 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 cost of 20,000 base units, which equals $0.02 per request (USDC uses 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 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 no further 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, detailed documentation, or example payloads were found, the actual data returned by this endpoint is unknown. The "medical/records" path suggests health-related data, which may carry regulatory implications (HIPAA, GDPR, etc.). Users should exercise caution and verify compliance requirements before integrating.
Capabilities
Use cases
- —Retrieving medical record data for record ID 44 on a per-call payment basis
- —Integrating health data into agent workflows without API key management
- —Programmatic access to medical records settled via crypto micropayments
Fit
Best for
- —Agents or applications needing on-demand medical record access without subscriptions
- —Developers experimenting with x402 pay-per-call protocols
- —Low-volume, ad-hoc medical data retrieval
Not for
- —Production healthcare systems requiring HIPAA-compliant, audited data pipelines
- —High-volume bulk medical record retrieval (no documented batch support)
- —Users who need detailed schema documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/44 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI spec, no request/response schema, no documentation beyond the landing page catalog, and the specific medical records endpoint is not even listed on the provider's homepage. The nature of the data returned is entirely unknown.
Warnings
- —No request or response schema available — actual data returned is unknown.
- —Path suggests medical/health data — potential HIPAA, GDPR, or other regulatory compliance concerns.
- —This specific endpoint (/api/v1/medical/records/44) is not listed on the provider's public API catalog page.
- —No documentation, examples, or README content could be retrieved (pages returned only 'Connect wallet').
Citations
- —Endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/44
- —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/44