Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific medical record (record ID 18) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
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. However, this specific endpoint (/api/v1/medical/records/18) is not listed on the provider's public landing page among the advertised API categories. It appears to be a medical records endpoint, which raises questions about the nature and sensitivity of the data returned. No documentation, request schema, or response schema is available beyond what the x402 challenge provides.
The endpoint is live and returns a proper x402 challenge with version 1. The payment timeout is 300 seconds (5 minutes). The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which is the canonical USDC address on Base.
Capabilities
Use cases
- —Retrieving a specific medical record (ID 18) via programmatic API call
- —Demonstrating x402 micropayment flows for data access
- —Agent-driven retrieval of health-related data with crypto payment
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing pay-per-call access to structured medical data
- —Projects exploring crypto-settled API micropayments
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Bulk retrieval of many medical records (only record 18 is addressed here)
- —Users without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/18 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the endpoint is not listed on the provider's own landing page. The medical records domain raises regulatory concerns with no compliance information available.
Warnings
- —This endpoint serves medical records but provides no documentation about data provenance, HIPAA compliance, or data sensitivity.
- —The endpoint /api/v1/medical/records/18 is not listed among the provider's publicly advertised APIs, raising questions about its intended availability.
- —No request body schema or response schema is documented — callers cannot know what to send or what to expect back.
- —Medical/health data may be subject to regulatory requirements (HIPAA, GDPR) that are not addressed by the provider.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/medical/records/18
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 is used for payment on Base.https://lowpaymentfee.com/api/v1/medical/records/18
- —The endpoint is not listed among the provider's publicly advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure).https://lowpaymentfee.com