Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 80) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
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. This specific endpoint falls under a "medical/records" path, but no documentation, schema, or sample responses are available to clarify what data fields are returned or what input the POST body expects. The endpoint is live and returns a well-formed 402 challenge, confirming it is operational.
Because no OpenAPI spec, request/response schema, or detailed documentation was found, the exact structure of requests and responses is unknown. The "medical" category in the URL path suggests health-related data, which may carry regulatory implications (e.g., HIPAA in the US). Prospective callers should exercise caution and verify compliance requirements before integrating.
Capabilities
Use cases
- —Retrieving medical record data for record ID 80 via a single paid API call
- —Integrating health data into agent workflows that support x402 micropayments
- —Programmatic access to medical records without traditional API key provisioning
Fit
Best for
- —Agents or applications that can settle x402 payments in USDC on Base
- —Developers needing quick, keyless access to medical record data
- —Micropayment-based data retrieval without subscription commitments
Not for
- —Use cases requiring documented request/response schemas before integration
- —Applications subject to strict healthcare data regulations (HIPAA) without prior compliance verification
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/80 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation, and no example payloads. The medical records path is undocumented and the data returned is entirely unknown. The regulated health-data category adds risk.
Warnings
- —No request or response schema available — input/output structure is completely unknown
- —Endpoint path suggests medical/health data which may be subject to HIPAA or other healthcare regulations
- —No documentation beyond the landing page listing; /api, /pricing, and /README pages are empty (wallet-connect only)
- —Record ID 80 is hardcoded in the endpoint path; unclear if other record IDs are accessible or what they represent
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/80
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/80