Pay-per-call medical records API on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/20`) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).
The provider site (lowpaymentfee.com) hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific medical records endpoint has no public documentation beyond its x402 challenge. There is no OpenAPI spec, no request/response schema, and no description of what data is returned or what input the POST body expects.
Because this endpoint deals with medical records — a regulated data category — users should exercise caution. There is no information about data provenance, compliance (e.g., HIPAA), or whether the data is synthetic, anonymized, or real. The endpoint is live and responds with a valid x402 402 challenge, but the lack of documentation makes it difficult to assess what you actually receive for your $0.02.
Capabilities
Use cases
- —Retrieving medical record data on a per-call basis without subscription
- —Integrating health data into agent workflows via x402 micropayments
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers exploring x402 payment protocol with real endpoints
- —Agents needing on-demand medical record lookups settled in USDC
- —Low-volume, pay-as-you-go access to health data
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Bulk medical data retrieval (no documented batch support)
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/20 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it accepts USDC on Base at $0.02/request. However, there is no OpenAPI spec, no request/response schema, no documentation of what the medical records endpoint actually returns, and no information about data provenance or compliance. This is effectively a stub listing.
Warnings
- —Medical/health data category — no compliance information (HIPAA, etc.) is provided
- —No documentation on request body format or response schema
- —No OpenAPI spec or examples available
- —Data provenance unknown — unclear if records are real, synthetic, or anonymized
- —The specific /medical/records/20 path is not listed on the provider's homepage catalog
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base network, maxAmountRequired 20000https://lowpaymentfee.com/api/v1/medical/records/20
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/20
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com