x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific medical record (record ID 89) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The provider site lowpaymentfee.com hosts a broad catalog of pay-per-request 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 endpoint being listed here (/api/v1/medical/records/89) is not mentioned on the provider's landing page among the advertised API categories. It appears to be a medical-records resource, but no documentation, request schema, or response schema is available. The actual data returned and the input parameters expected in the POST body are unknown.
Because this endpoint deals with medical records, users should exercise caution regarding data authenticity, regulatory compliance (e.g., HIPAA in the US), and the sensitivity of health-related information. No OpenAPI spec, examples, or detailed documentation were found during the crawl.
Capabilities
Use cases
- —Retrieving a specific medical record (ID 89) via a paid API call
- —Integrating health record lookups into agent workflows with crypto micropayments
- —Accessing medical data without API key registration
Fit
Best for
- —Agents needing on-demand medical record access with crypto payment
- —Developers exploring x402 pay-per-request patterns for health data
- —Scenarios requiring keyless, instant API access on Base network
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of many medical records (only record 89 is addressed by this endpoint)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/89 \
-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 documentation, no request/response schema, no examples, and the specific medical-records path is not listed on the provider's own landing page. The nature and authenticity of the data returned is completely unknown, and the endpoint touches a regulated category (health/medical data).
Warnings
- —No documentation or schema available for this endpoint — request body and response format are unknown.
- —This endpoint serves medical records, a regulated data category. No information about data provenance, compliance (HIPAA, GDPR), or data authenticity is provided.
- —The /api/v1/medical/records/89 path is not listed among the provider's advertised APIs on the landing page, raising questions about whether it is an officially supported endpoint.
- —No OpenAPI spec, README, or detailed docs were accessible during the crawl.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/medical/records/89
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/89