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/86` 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 86), 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 flat pricing of $0.02/request advertised on the landing page. The platform markets itself as requiring no API keys, no rate limits, and no commitments — just an x402 payment header per call. The payment timeout is 300 seconds.
Important caveats: there is no OpenAPI schema, no documentation beyond the landing page listing, and no sample request/response bodies available. The endpoint path suggests it returns medical record data, which falls into a regulated category (health data). There is no information about the provenance, format, or compliance status of the data returned. Prospective callers should exercise caution and verify the nature of the data before integrating.
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 records via x402 micropayments
Fit
Best for
- —Agents or applications needing on-demand medical record lookups
- —Developers exploring x402 pay-per-call patterns on Base
- —Low-volume, no-commitment access to health data endpoints
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —High-volume bulk medical data retrieval (no documented batch support)
- —Users who need detailed documentation or schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/86 \
-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 zero documentation on request/response schemas, no OpenAPI spec, no examples, and the endpoint deals with medical records — a regulated category — with no compliance or provenance information. The listing is effectively a stub with a confirmed payment challenge.
Warnings
- —Regulated category: endpoint path suggests medical/health record data with no documented compliance (HIPAA, etc.)
- —No OpenAPI schema or request/response documentation available
- —No sample responses; actual data format and content are unknown
- —The specific record ID (86) is hardcoded in the path — unclear if this is a demo or production resource
- —Provider site pages beyond the landing page returned only 'Connect wallet' with no useful content
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/86
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/86
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com