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 61) behind an x402 payment wall. 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/61) 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 for it. The actual data returned and the required POST body are unknown.
Because this endpoint deals with medical records, it may involve sensitive health data. There is no visible privacy policy, HIPAA compliance statement, or data-handling documentation on the provider site. Users should exercise caution and verify the nature and legitimacy of the data before relying on it in any regulated context.
Capabilities
Use cases
- —Retrieving a specific medical record (ID 61) via a single paid API call
- —Demonstrating x402 micropayment flows against a live endpoint
- —Integrating pay-per-request health data into an agent workflow
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch structured medical record data on demand
- —Low-cost, keyless API access without subscription commitments
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling
- —Bulk retrieval of many medical records (only record 61 is exposed at this path)
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/61 \
-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 medical records path is not listed on the provider's own site. The nature of the data is entirely unknown, and the medical category raises regulatory concerns with zero compliance information.
Warnings
- —Medical/health data endpoint with no visible HIPAA compliance or privacy documentation
- —Endpoint path /api/v1/medical/records/61 is not listed among the provider's advertised APIs
- —No request body schema or response schema available — input/output format is unknown
- —No OpenAPI spec, no README content, and no detailed docs found on the provider site
- —Regulated data category (medical records) — verify legitimacy and legal compliance before use
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, on Base network, requiring up to 20000 base units of USDChttps://lowpaymentfee.com/api/v1/medical/records/61
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/61
- —Provider site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider's landing page lists Data & Analytics, AI & ML, Finance & Web3, and Infrastructure API categories but does not list medical records endpointshttps://lowpaymentfee.com