Pay-per-call medical records endpoint on Base via x402 (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource at path `/api/v1/medical/records/90` using the x402 payment protocol. It is live and returns a 402 challenge requiring payment in USDC on the Base network. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD per request.
The provider site lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This specific endpoint falls under a "medical records" path, but no documentation, request schema, or response schema is provided beyond the generic "Premium API Access" label. The endpoint accepts POST requests and returns `application/json`.
Because there is no OpenAPI spec, no request/response examples, and no documentation explaining what data this endpoint actually returns or what input it expects, the practical utility is unclear. The "medical records" path name raises regulatory concerns (PHI/HIPAA), and there is no indication of compliance or data provenance. Users should exercise caution and verify the nature of the data before relying on this endpoint for anything involving protected health information.
Capabilities
Use cases
- —Retrieving medical record data for record ID 90 via a single paid API call
- —Integrating pay-per-call health data into agent workflows
- —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 medical record lookups without API key management
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —High-volume batch medical data processing (no documented rate limits but no SLA either)
- —Users who need detailed request/response documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/90 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation, and no examples. The 'medical records' label is unexplained, raising regulatory red flags. Effectively a stub listing.
Warnings
- —No request or response schema available — unclear what input is expected or what data is returned.
- —Path suggests medical/health data (PHI) — no HIPAA compliance or data provenance information provided.
- —No OpenAPI spec, no documentation pages, no examples found on the provider site.
- —The provider site lists many diverse API categories at uniform $0.02 pricing with no substantive docs for any of them — exercise caution regarding data quality and legitimacy.
Citations
- —Endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/90
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/90
- —Provider advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com