x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at `/api/v1/medical/records/55` is part of the lowpaymentfee.com platform, a collection of x402 protocol pay-per-call APIs settled on the Base network using USDC. The specific endpoint appears to serve medical record data (record ID 55) behind a paywall. The x402 challenge is live and returns a 402 with an `exact` payment scheme requiring up to 20,000 base units of USDC (0x8335…) on Base, which equals $0.02 USD (USDC uses 6 decimals). Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout.
The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing model across dozens of endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility categories. All endpoints use the x402 protocol with no API keys, no rate limits, and no commitments required. However, the specific `/api/v1/medical/records/55` endpoint is not listed on the site's landing page among the advertised APIs, which raises questions about its purpose and whether it returns real or synthetic data.
No OpenAPI schema, request body documentation, or response examples are available for this endpoint. The `outputSchema` in the x402 challenge only indicates it accepts HTTP POST requests and is discoverable. The lack of documentation about what data this endpoint returns, what POST body it expects, and the sensitive nature of "medical records" data should be noted. Users should exercise caution and verify the nature of the data before relying on this endpoint.
Capabilities
Use cases
- —Retrieving medical record data via a single pay-per-call transaction
- —Testing x402 protocol integrations with a low-cost endpoint
- —Agent-driven data retrieval workflows that need medical record access
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing pay-per-call access without API key management
- —Low-volume, on-demand medical data retrieval
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Bulk medical data retrieval at scale (no documented batch support)
- —Users who need detailed API documentation or response schema before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/55 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation for request body, response schema, or what data is actually returned. The endpoint is not listed among the provider's advertised APIs, and the 'medical records' category raises regulatory concerns with zero compliance documentation.
Warnings
- —Endpoint not listed on provider's public API catalog — may be undocumented, experimental, or synthetic data
- —'Medical records' implies health data — no HIPAA compliance, data provenance, or privacy documentation found
- —No request body schema or response schema available; unclear what POST body is expected
- —No OpenAPI spec, no examples, no README content (pages behind wallet connect)
- —Data authenticity unknown — could be synthetic/demo data
Citations
- —The x402 challenge requires up to 20,000 base units of USDC on Base network with a 300-second timeouthttps://lowpaymentfee.com/api/v1/medical/records/55
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/55
- —Platform advertises $0.02/request uniform pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The /api/v1/medical/records/55 endpoint is not listed among the provider's publicly advertised APIshttps://lowpaymentfee.com