Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at `/api/v1/medical/records/28` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. All endpoints use the x402 protocol for payment, settling in USDC on the Base network with no API keys, no rate limits, and no subscriptions required.
The specific resource at `/api/v1/medical/records/28` is labeled "Premium API Access" and accepts POST requests. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD per request), consistent with the site-wide $0.02/request pricing. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), with a 300-second payment timeout.
Important caveats: the endpoint path suggests it returns medical records, but no documentation, request schema, or response schema is available beyond the generic "Premium API Access" label. The crawled site pages (pricing, README, /api) all returned only a "Connect wallet" prompt with no further detail. Without concrete documentation on what data this endpoint actually returns, its input parameters, or its data sources, treat this listing with caution. The endpoint is live (returns a valid 402 challenge), but its actual functionality and data content are unverified.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Agent-driven access to health-related data without subscription or API key
- —Programmatic access to record #28 via x402 micropayment
Fit
Best for
- —Agents needing one-off medical record lookups without credential setup
- —Developers testing x402 payment flows against a live endpoint
- —Low-volume, pay-as-you-go access to health data
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Bulk retrieval of large medical datasets
- —Use cases requiring detailed schema documentation or SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/28 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no request/response schema, no examples, and the "medical records" label is unexplained. The crawled pages beyond the homepage returned no useful content. This is effectively a stub listing.
Warnings
- —No request or response schema available — actual data returned is unknown
- —Endpoint labeled 'medical records' but no documentation explains data source, format, or compliance status
- —Potential regulatory concern: medical/health data may be subject to HIPAA or similar regulations — no compliance information provided
- —Site pages (/api, /pricing, /README) returned only 'Connect wallet' with no documentation
- —The specific record ID '28' in the path is hardcoded with no explanation of what it references
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/28
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/28