x402-gated medical records endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com serves medical record data behind an x402 paywall. The specific resource `/api/v1/medical/records/35` returns JSON content upon payment. It uses the x402 protocol (version 1) with the "exact" payment scheme, settling on the Base network in USDC (contract 0x8335…2913). The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The provider's landing page lists a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, infrastructure utilities, and more — all priced at $0.02 per request. However, this specific endpoint (`/api/v1/medical/records/35`) is not listed on the provider's public catalog page, and the endpoint path suggests it returns a specific medical record (record ID 35). No OpenAPI schema, request body documentation, or response examples are available for this endpoint. The POST method is indicated in the outputSchema.
Because this endpoint deals with medical records, it likely involves sensitive health data. There is no documentation about data provenance, compliance (e.g., HIPAA), or what the returned record actually contains. Callers should exercise caution and understand the regulatory implications of accessing or processing medical data through a minimally documented third-party API.
Capabilities
Use cases
- —Retrieving a specific medical record (ID 35) via programmatic API call
- —Agent-driven workflows that need on-demand access to medical data
- —Demonstrating x402 micropayment protocol for data access
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access to structured medical data
- —Proof-of-concept integrations with crypto-settled APIs
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees
- —Bulk retrieval of large medical datasets
- —Users who need detailed API documentation or schema validation before calling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/35 \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request/response schema, no OpenAPI spec, no examples, and the endpoint is not listed in the provider's own catalog. The medical records category raises regulatory concerns with no compliance information provided.
Warnings
- —Endpoint path suggests medical/health data — no HIPAA or regulatory compliance information is documented.
- —This specific endpoint (/api/v1/medical/records/35) is not listed on the provider's public catalog page.
- —No request body schema or response schema documentation available.
- —No OpenAPI specification found.
- —Data provenance and authenticity of medical records is unknown.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/medical/records/35
- —The provider's landing page lists APIs at $0.02 per request across multiple categories.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/medical/records/35