Pay-per-call medical records API on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 73) 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 an exact-scheme challenge requiring up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals).
The provider, 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. The specific endpoint `/api/v1/medical/records/73` is not listed on the provider's public landing page among the advertised categories, so its exact response schema and data contents are unknown. The x402 challenge confirms the endpoint is live and accepting payment-gated requests.
Because there is no OpenAPI spec, no documentation beyond the landing page, and no example responses available, the actual structure and content of the medical records payload cannot be verified. Users should exercise caution given the sensitive nature of medical data and the lack of documentation about data provenance, compliance (e.g., HIPAA), or access controls beyond the payment gate.
Capabilities
Use cases
- —Retrieving medical record data for record ID 73 via a single paid API call
- —Integrating pay-per-request medical data access into agent workflows
- —Demonstrating x402 payment-gated access to sensitive data endpoints
Fit
Best for
- —Agents or developers needing on-demand medical record access without subscription
- —x402-compatible wallets looking for low-cost per-call data endpoints
- —Prototyping payment-gated access to health data
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of many medical records (single record ID hardcoded in URL)
- —Users who need detailed API documentation or response schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/73 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and confirms pricing and network, but there is no OpenAPI spec, no response schema, no documentation for this specific endpoint, and the endpoint is not listed on the provider's own landing page. The medical/health category raises compliance concerns with zero documentation.
Warnings
- —Endpoint /api/v1/medical/records/73 is not listed among the provider's publicly advertised APIs — its data source and legitimacy are unverified.
- —No documentation exists for the response schema or data contents of this medical records endpoint.
- —Medical data may be subject to HIPAA or other regulatory requirements; no compliance information is provided.
- —No OpenAPI spec or example responses are available; response structure is entirely unknown.
- —Hardcoded record ID (73) in the URL — unclear if other record IDs are accessible or how discovery works.
Citations
- —The x402 challenge returns a 402 with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/medical/records/73
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/medical/records/73
- —The /api/v1/medical/records/73 endpoint is not listed among the provider's publicly advertised API categories.https://lowpaymentfee.com