Pay-per-call medical records endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/79` is part of the lowpaymentfee.com platform, which hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific endpoint probed appears to serve medical record data (record ID 79) behind a micropayment wall. 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. USDC uses 6 decimals, so the per-request cost is $0.02 — consistent with the site-wide flat pricing of $0.02 per request. The endpoint accepts HTTP POST, requires no API keys, and claims no rate limits. A 5-minute (300 s) payment timeout is specified.
Important caveats: the endpoint is labeled "medical/records," which suggests it may return health-related data. No OpenAPI schema, request/response examples, or detailed documentation were found in the crawl. The `/api`, `/pricing`, and `/README` pages all returned only a "Connect wallet" prompt with no substantive content. Without documentation it is impossible to confirm what data the endpoint actually returns, what POST body it expects, or whether the data involves real patient information (which would implicate HIPAA and similar regulations).
Capabilities
Use cases
- —Retrieving medical record data behind a per-call micropayment
- —Demonstrating x402 payment flows for data access
- —Integrating pay-per-request health data into agent workflows
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need on-demand data access without API key provisioning
- —Low-volume, pay-as-you-go data retrieval on Base
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling
- —High-volume bulk medical data retrieval (no documented batch support)
- —Users who need detailed API documentation or response schemas before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/79 \
-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). However, there is no OpenAPI schema, no request/response examples, and no meaningful documentation — the docs pages all resolve to a wallet-connect prompt. The medical-records domain raises regulatory concerns that are unaddressed.
Warnings
- —No API documentation, OpenAPI spec, or response schema available — request body format and response structure are unknown.
- —Endpoint path suggests medical/health data; potential HIPAA or health-data-regulation implications are not addressed anywhere on the site.
- —All documentation pages (/api, /pricing, /README) returned only a 'Connect wallet' prompt with no content.
- —The specific record ID (79) is hardcoded in the path; it is unclear how to discover or enumerate other records.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/79
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/79