Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/91` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific endpoint probed appears to serve medical record data (record ID 91), accepting POST requests and returning JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.
The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site-wide pricing of $0.02/request displayed on the landing page. The platform advertises no API keys, no rate limits, and instant access — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
Important caveat: the endpoint path suggests it returns medical records, which falls into a regulated data category (health/PHI). No documentation, OpenAPI schema, or example responses were found in the crawl. The landing page lists many API categories but does not specifically list or describe this medical records endpoint, so its actual data content, input parameters, and response format are unknown. Treat with caution.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Integrating health record lookups into agent workflows without API key management
- —Programmatic access to structured medical data settled via crypto micropayments
Fit
Best for
- —Agents needing on-demand medical record access with no subscription
- —Developers prototyping health data integrations with minimal setup
- —Crypto-native applications that settle payments on Base L2
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees (no compliance documentation found)
- —Use cases needing bulk/batch medical record retrieval at scale
- —Users who need detailed API documentation or response schema before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/91 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation, no example request/response, and the medical records category raises regulatory concerns with zero compliance information available. The endpoint is not even listed on the provider's own landing page catalog.
Warnings
- —Medical/health data endpoint with no HIPAA or compliance documentation found
- —Endpoint path /api/v1/medical/records/91 is not listed on the provider's landing page among advertised APIs
- —No OpenAPI spec, request schema, or response schema available — input parameters and output format are completely unknown
- —Regulated data category: callers should verify legal and compliance requirements before use
- —No robots.txt or agents.txt found; no usage terms documented
Citations
- —x402 challenge returns 402 with maxAmountRequired of 20000 USDC base units on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/91
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/91
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Landing page lists Data & Analytics, AI & ML, Finance & Web3, and Infrastructure API categories but does not list medical records endpointshttps://lowpaymentfee.com