Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 72) 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 endpoint is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. Payment is handled entirely through the x402 protocol's X-PAYMENT header mechanism on the Base L2 network.
Important caveats: The specific endpoint path references "medical/records/72," which suggests health-related data. No documentation, OpenAPI schema, or example responses were found beyond the 402 challenge and the site's landing page. The actual data returned by this endpoint is unknown — it could be synthetic/demo data or real medical records. Users should exercise caution given the sensitive nature of medical data and the complete absence of documentation about data provenance, compliance (HIPAA, etc.), or content format.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without API key management
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand data access without subscription commitments
- —Low-volume, pay-as-you-go medical data retrieval
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —High-volume bulk medical data extraction (no documented rate limits but no SLA either)
- —Users who need detailed API documentation or schema validation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/72 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request/response schemas, no OpenAPI spec, no example payloads, and the medical records context raises regulatory concerns with no compliance information provided.
Warnings
- —No API documentation, OpenAPI schema, or example responses available
- —Endpoint serves medical/health data — no HIPAA or regulatory compliance information found
- —Actual content and data provenance of 'medical records' is completely unknown
- —The /api, /pricing, and /README pages all returned only a 'Connect wallet' prompt with no useful content
- —This may be a demo or placeholder endpoint rather than a production medical data service
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/72
- —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/72