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 31) 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 sits under the /api/v1/medical/records path, but the landing page does not list it among its advertised categories, and no documentation describes the request body schema or the structure of the returned medical record data. The endpoint is live (returns a 402 challenge as expected for x402), but the lack of any input/output schema documentation or example payloads limits its practical discoverability.
Because this endpoint deals with medical records, consumers should be aware of potential regulatory considerations (e.g., HIPAA in the US, GDPR in the EU) depending on the nature of the data returned. The provider offers no visible privacy policy, terms of service, or compliance documentation in the crawled material.
Capabilities
Use cases
- —Retrieving medical record data for record ID 31 via a single paid API call
- —Integrating pay-per-use medical data access into agent workflows
- —Programmatic access to health records without subscription or API key management
Fit
Best for
- —Agents needing on-demand medical record lookups settled in crypto
- —Developers prototyping x402 payment flows with real endpoints
- —Use cases requiring keyless, pay-as-you-go API access on Base
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling with audit trails
- —Bulk retrieval of large medical datasets (pay-per-call model is per-record)
- —Users who need detailed API documentation or schema validation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/31 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the medical records path is not even listed on the provider's own landing page. The regulated nature of medical data with no compliance information further lowers confidence.
Warnings
- —No request body schema or response schema documented — callers have no way to know what to send or what they will receive.
- —Medical records endpoint is not listed among the provider's advertised API categories, raising questions about its status.
- —No privacy policy, terms of service, or regulatory compliance documentation (HIPAA, GDPR) found despite dealing with medical data.
- —This endpoint handles potentially sensitive health information — exercise caution and verify data provenance before use.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/31
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/31
- —The medical records endpoint is not listed among the provider's advertised API categories on the landing pagehttps://lowpaymentfee.com