x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 99) behind an x402 payment wall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (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, crypto, infrastructure utilities, and more — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the `/api/v1/medical/records/99` path, which is not listed on the provider's public catalog page. No documentation, request/response schema, or example payloads are available for this endpoint. It is unclear what data this endpoint returns, what input it expects in the POST body, or whether it serves real medical data or placeholder/demo content.
The endpoint is confirmed live: the probe received a proper HTTP 402 x402 challenge with version 1 headers. The root site returns HTTP 200. No OpenAPI spec, ai-plugin manifest, or agents.txt was found.
Capabilities
Use cases
- —Retrieving medical record data for record ID 99 via a single paid API call
- —Demonstrating x402 micropayment flows against a medical data endpoint
- —Integrating pay-per-request health data into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record retrieval without API keys
- —Testing micropayment-gated data access patterns
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees (no compliance info available)
- —Bulk medical data retrieval or batch processing (single-record endpoint)
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/99 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and the specific medical records path is not listed on the provider's own catalog. The nature and legitimacy of the data returned is entirely unknown. This is effectively a stub listing.
Warnings
- —No documentation or schema available for this endpoint — request body and response format are unknown.
- —The /api/v1/medical/records/99 path is not listed on the provider's public catalog; it may be a demo or placeholder.
- —Endpoint claims to serve 'medical records' but no compliance, privacy, or data-source information is provided.
- —This may involve regulated health data — exercise caution regarding HIPAA and other healthcare data regulations.
- —No examples, no OpenAPI spec, no agents.txt, no ai-plugin manifest found.
Citations
- —The endpoint returns HTTP 402 with x402 version 1 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/99
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/medical/records/99
- —The provider advertises all APIs at $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider's catalog lists analytics, AI/ML, finance, crypto, and utility endpoints but does not list /api/v1/medical/records/99https://lowpaymentfee.com