x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com serves medical record data behind an x402 paywall. The specific resource `/api/v1/medical/records/16` returns JSON content upon payment. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all settled via USDC on the Base network.
The x402 challenge confirms the endpoint is live and accepts payment via the "exact" scheme on Base. The maximum amount required is 20,000 base units of USDC (contract 0x8335…2913), which equals $0.02 USD (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
No OpenAPI schema, request body documentation, or response examples are available for this specific medical records endpoint. The landing page lists it under no visible category (it does not appear on the homepage's catalog), so its exact data contents and required input fields are unknown. The "medical/records" path suggests health-related data, which may carry regulatory implications (HIPAA, etc.). Use with caution and verify the provider's data handling practices independently.
Capabilities
Use cases
- —Retrieving medical record data for record ID 16 via a single paid API call
- —Integrating health data into agent workflows that support x402 payment
- —Programmatic access to structured medical information without API keys
Fit
Best for
- —Agents or applications that need on-demand medical record lookups
- —Developers experimenting with x402 payment-gated health data APIs
- —Low-volume, pay-as-you-go access to medical records
Not for
- —Production healthcare systems requiring HIPAA-compliant data pipelines
- —Bulk retrieval of large medical datasets (single-record endpoint)
- —Users who cannot transact in USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/16 \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation for request/response schema, no OpenAPI spec, no examples, and the medical records path does not appear in the provider's own catalog. The health data category raises regulatory concerns with zero transparency on data sourcing or compliance.
Warnings
- —No request or response schema documented for this endpoint
- —Endpoint path suggests medical/health data — verify HIPAA and regulatory compliance independently
- —This specific endpoint (/api/v1/medical/records/16) is not listed on the provider's homepage catalog
- —No information on what data is returned or what input fields are expected in the POST body
- —Provider identity and data sourcing practices are opaque
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeouthttps://lowpaymentfee.com/api/v1/medical/records/16
- —The platform advertises $0.02 per 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/16