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 (`/api/v1/medical/records/9`) 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 a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
The provider's landing page advertises a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required. This specific endpoint falls under a "medical/records" path that is not listed on the homepage, so its exact data content and response schema are unknown. No OpenAPI spec, detailed documentation, or example responses were found during the crawl.
Because this endpoint deals with medical records, consumers should exercise caution regarding data provenance, accuracy, and regulatory compliance (e.g., HIPAA in the US). The lack of documentation about what data is returned, how it is sourced, and what record ID "9" represents makes it difficult to assess fitness for any particular use case.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without API key management
- —Programmatic access to structured medical information
Fit
Best for
- —Agents needing on-demand medical record lookups with crypto micropayments
- —Developers exploring x402 payment protocol integrations
- —Use cases where no-signup, pay-per-call access is preferred
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed documentation or guaranteed SLAs before integration
- —Bulk medical data retrieval at scale (no documented batch endpoints)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/9 \
-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), but there is no OpenAPI spec, no documentation, no example responses, and the medical records path is not even listed on the provider's own homepage. The nature and source of the data are entirely unknown, and the health/medical category raises regulatory concerns.
Warnings
- —Medical/health data category — verify regulatory compliance (HIPAA, GDPR) before use in production.
- —No documentation or schema available for request body or response format.
- —The /api/v1/medical/records/9 path is not listed on the provider's homepage; its data content is unknown.
- —Record ID '9' is hardcoded in the endpoint path; unclear if other IDs are available or what they represent.
- —No OpenAPI spec, README, or API docs were accessible during crawl.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC payment on Base network at 20,000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/9
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/9