Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at `/api/v1/medical/records/95` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs accessible via the x402 payment protocol on the Base network. The specific endpoint appears to serve medical record data (record ID 95) and accepts POST requests. Payment is settled in USDC on Base, with a maximum cost of $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys or rate limits are advertised; callers pay per request using an X-PAYMENT header.
The broader lowpaymentfee.com platform lists endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all at the same $0.02/request price point. However, the specific `/api/v1/medical/records/95` endpoint is not listed on the site's landing page among the advertised APIs, and no documentation, request schema, or response schema is provided for it. The endpoint is live (returns a valid 402 x402 challenge), but the nature and format of the medical record data it returns is unknown. The "medical/records" path suggests health-related data, which may carry regulatory implications (e.g., HIPAA in the US).
Capabilities
Use cases
- —Retrieving medical record data for record ID 95 via a single paid API call
- —Integrating health record lookups into agent workflows that support x402 payments
- —Programmatic access to medical data without subscription or API key management
Fit
Best for
- —Agents or applications needing on-demand medical record access with crypto micropayments
- —Developers exploring x402 pay-per-call patterns for health data
- —Use cases where avoiding API key provisioning is desirable
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of many medical records (single-record endpoint, pay-per-call)
- —Users who need detailed documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/95 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no request/response schema, and the endpoint is not listed among the site's advertised APIs. The 'medical records' path raises regulatory concerns with zero supporting documentation. Effectively a stub listing.
Warnings
- —No request or response schema available — the data format returned is completely unknown.
- —The /api/v1/medical/records/ path implies health data, which may be subject to HIPAA or other health data regulations. No compliance information is provided.
- —This specific endpoint is not listed on the provider's landing page among advertised APIs; its provenance and data source are unclear.
- —No documentation, examples, or README content could be retrieved from the site (pages returned only 'Connect wallet').
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/95
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/95