Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402 endpoint at lowpaymentfee.com provides access to a medical records resource at `/api/v1/medical/records/87`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers include an `X-PAYMENT` header with a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. No API keys or rate limits are advertised; access is gated purely by payment.
The specific resource (`/medical/records/87`) suggests a single record lookup, but no documentation exists describing the request body schema, response fields, or what medical data is returned. The platform's landing page lists this endpoint's category implicitly under its broader API catalog, but the medical records path is not explicitly listed among the advertised categories (analytics, AI, finance, infrastructure). There is no OpenAPI spec, no example requests or responses, and no detailed documentation available from the crawl.
Capabilities
Use cases
- —Retrieving a specific medical record by ID via programmatic API call
- —Integrating medical data lookups into agent workflows with per-call crypto payment
- —Accessing health records without pre-registration or API key management
Fit
Best for
- —Agents or applications needing on-demand medical record access with crypto micropayments
- —Developers prototyping health data integrations without subscription commitments
- —x402-compatible clients on the Base network
Not for
- —Production healthcare applications requiring HIPAA compliance guarantees (no compliance documentation available)
- —Bulk medical data retrieval or batch processing (pay-per-call model, no batch endpoint documented)
- —Users without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/87 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-signed-payment>"Endpoint
Quality
The endpoint is live (returns 402 with a valid x402 challenge), but there is no OpenAPI spec, no documentation of request/response schemas, no examples, and the medical records path is not listed among the provider's advertised APIs. The nature and legitimacy of the medical data is entirely unknown. This is effectively a stub listing.
Warnings
- —No documentation exists for the /api/v1/medical/records/ path — it is not listed among the provider's advertised API categories.
- —No request body schema or response schema is documented; callers have no way to know what to send or what they will receive.
- —Medical/health data endpoint with zero compliance, privacy, or regulatory documentation — exercise extreme caution.
- —The endpoint may contain synthetic or placeholder data; legitimacy cannot be verified from available materials.
- —No OpenAPI spec or AI plugin manifest available.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/medical/records/87
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC contract on Base at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 uses 6 decimals, so 20000 base units = $0.02.https://lowpaymentfee.com