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 (record ID 76) via the x402 payment protocol. The endpoint 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 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 available beyond the x402 challenge metadata. The response MIME type is application/json and the HTTP method is POST.
Because no OpenAPI spec, request body schema, or example responses are provided, it is unclear what input the endpoint expects or what medical record data it returns. The "medical" categorization raises regulatory and sensitivity concerns (e.g., HIPAA, PHI). Users should exercise caution and verify the nature and legitimacy of the data before relying on this endpoint in any production or compliance-sensitive context.
Capabilities
Use cases
- —Retrieving medical record data for record ID 76 via a single paid API call
- —Integrating pay-per-call medical data access into agent workflows
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Agents needing on-demand, keyless API access to medical record data
- —Prototyping pay-per-call data retrieval pipelines
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Use cases needing bulk or batch medical record retrieval
- —Applications requiring detailed API documentation or SLAs
Quick start
# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# POST https://lowpaymentfee.com/api/v1/medical/records/76
# Cost: $0.02 per request (USDC on Base)
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/76 \
-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 no OpenAPI spec, no request/response schema, no documentation, and no example payloads. The medical records category raises regulatory red flags with zero compliance information available.
Warnings
- —No request or response schema documented — input format is unknown
- —Medical/health data endpoint with no HIPAA or compliance information provided
- —No OpenAPI spec or detailed documentation available from the provider
- —The specific record ID (76) is hardcoded in the path; unclear if other IDs are accessible
- —Provider site pages (/api, /pricing, /README) returned only 'Connect wallet' with no useful content
Citations
- —Endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/76
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/76