Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at `/api/v1/medical/records/78` 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. All endpoints use the x402 protocol for payment, settling in USDC on the Base network with no API keys, no rate limits, and no subscriptions required.
The specific resource at `/api/v1/medical/records/78` is labeled "Premium API Access" and accepts POST requests. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD per request, since USDC uses 6 decimals). Payment is sent to the on-chain address `0x1A2B...85F3` on Base, with a timeout of 300 seconds. The response MIME type is `application/json`.
Important caveats: the endpoint path suggests it returns medical records, which falls into a regulated data category (health/PHI). No documentation, OpenAPI schema, or example responses are available beyond the x402 challenge metadata and the landing page listing. There is no information about what data is actually returned, what POST body is expected, or whether the data involves real patient information. Prospective users should exercise caution and verify compliance with applicable health data regulations before use.
Capabilities
Use cases
- —Retrieving medical record data for record ID 78 via a single paid API call
- —Integrating health data into agent workflows that support x402 micropayments
- —Programmatic access to medical records without subscription or API key management
Fit
Best for
- —Agents or applications that need on-demand medical record access via crypto micropayments
- —Developers exploring x402 protocol integrations on Base
- —Use cases where keyless, pay-per-request access is preferred over subscription APIs
Not for
- —Production healthcare applications requiring HIPAA or equivalent compliance guarantees (no compliance documentation available)
- —Users who need detailed API documentation, request/response schemas, or SLAs
- —Bulk or high-volume medical data retrieval (no batch endpoints documented)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/78 \
-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/request in USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond the landing page, and the endpoint path implies regulated health data with zero compliance information provided.
Warnings
- —Endpoint path suggests medical/health records — regulated data category (HIPAA, GDPR health provisions). No compliance or data provenance documentation found.
- —No OpenAPI spec, request body schema, or response schema available. It is unknown what POST body is expected or what data is returned.
- —The specific record ID '78' is hardcoded in the path; it is unclear whether this is a demo, a single fixed resource, or parameterizable.
- —No robots.txt or agents.txt found; no terms of service or privacy policy discovered in crawl.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/78
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02 per requesthttps://lowpaymentfee.com/api/v1/medical/records/78
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeouthttps://lowpaymentfee.com/api/v1/medical/records/78