Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/74` 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. The specific endpoint probed here appears to serve medical record data (record ID 74), accepting POST requests and returning JSON. Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 "exact" scheme.
The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site-wide flat pricing of $0.02/request. The platform advertises no API keys, no rate limits, and instant access — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof. The payment timeout is 300 seconds.
Important caveat: the endpoint path suggests it returns medical records, which is a regulated data category. No documentation, OpenAPI schema, or sample responses were found beyond the x402 challenge and the provider's landing page. The actual content and compliance posture of this endpoint are unknown. There is no robots.txt or agents.txt, and subpages (/api, /pricing, /README) returned only a wallet-connect prompt with no substantive content.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Integrating health record lookups into agent workflows without API key management
- —Programmatic access to medical records with crypto-native micropayments
Fit
Best for
- —Agents or applications needing on-demand medical record access with no subscription
- —Developers wanting keyless, pay-per-use API access on Base
- —Crypto-native workflows that can attach x402 payment headers
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation or schema validation before integration
- —High-volume batch retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/74 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation, no OpenAPI schema, no example requests or responses, and the endpoint deals with medical records — a regulated category — with no compliance information available.
Warnings
- —Medical/health data endpoint with no documentation on data provenance, compliance (e.g., HIPAA), or content structure.
- —No OpenAPI spec, no example responses, and no substantive documentation found on the site.
- —Subpages (/api, /pricing, /README) returned only a wallet-connect prompt — no useful content.
- —The specific record ID (74) is hardcoded in the path; it is unclear how to discover or query other records.
- —Regulated data category: callers should independently verify legal and compliance requirements before use.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/74
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/74