Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This x402 endpoint at lowpaymentfee.com serves medical record data behind a per-request micropayment wall. The specific resource `/api/v1/medical/records/83` returns JSON and is accessed via HTTP POST. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 "exact" scheme.
The endpoint advertises a maxAmountRequired of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request — consistent with the provider's site-wide pricing of $0.02/request across all their API categories. The provider claims no API keys, no rate limits, and instant access; callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider hosts a broad catalog of endpoints spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all at the same $0.02 price point. However, this particular endpoint falls under a "medical records" path. No documentation, OpenAPI spec, or response schema is available for this endpoint beyond the x402 challenge metadata. The actual structure of the medical record data returned is unknown, and the legitimacy or nature of the medical data served is unclear.
Capabilities
Use cases
- —Retrieving medical record data for record ID 83 via a single micropayment
- —Integrating pay-per-call health data access into agent workflows
- —Demonstrating x402 micropayment protocol usage on Base
Fit
Best for
- —Agents needing on-demand medical record retrieval without API key signup
- —Developers experimenting with x402 payment protocol on Base
- —Applications requiring low-cost per-call data access
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data sources
- —Bulk retrieval of large medical datasets (pay-per-call model adds up)
- —Users who need detailed API documentation or response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/83 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no response schema, no documentation for this specific endpoint, and the nature/legitimacy of "medical records" data is entirely unknown. The crawled pages beyond the homepage returned only "Connect wallet" with no useful content.
Warnings
- —No API documentation, OpenAPI spec, or response schema available for this endpoint.
- —The endpoint serves 'medical records' data — the provenance, accuracy, and regulatory compliance (e.g., HIPAA) of this data is completely unknown.
- —The specific record ID (83) is hardcoded in the path; it is unclear whether other record IDs exist or what data they contain.
- —No examples of request body or response body are available anywhere in the crawled material.
- —This may be a demo/placeholder endpoint rather than a production medical data source.
Citations
- —The endpoint returns HTTP 402 with x402 challenge advertising USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/83
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/medical/records/83
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/83