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 specific medical record resource (`/api/v1/medical/records/34`) via POST. Payment is settled on the Base network using USDC (contract `0x8335…2913`) through the x402 exact-payment scheme. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD — consistent with the provider's site-wide flat pricing of $0.02 per request.
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 — as seen here — medical records. All endpoints share the same pricing model: no API keys, no rate limits, no subscriptions, just a per-request USDC micropayment on Base. The x402 challenge was successfully captured (HTTP 402 with valid accepts payload), confirming the endpoint is live.
However, there is no documentation, OpenAPI schema, or example request/response for this specific medical records endpoint. The crawled pages beyond the landing page returned only a "Connect wallet" prompt with no additional content. The nature of the data returned (what fields, format, whether record ID 34 is a real or demo resource) is entirely unknown. The "medical/records" path suggests health-related data, which may carry regulatory implications (HIPAA, etc.). Prospective callers should exercise caution and verify the data's nature and compliance status before use.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Agent-driven health data lookups without API key provisioning
- —Programmatic access to structured medical information via micropayment
Fit
Best for
- —Agents or applications needing on-demand medical record access without subscriptions
- —Developers exploring x402 micropayment patterns on Base
- —Low-volume, pay-as-you-go health data retrieval
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk medical data exports or high-throughput batch processing
- —Users who need detailed documentation or schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/34 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured with valid x402 payload and clear pricing), but there is zero documentation, no OpenAPI schema, no example requests or responses, and the nature of the returned data is completely unknown. The medical records category raises regulatory concerns that are unaddressed.
Warnings
- —No documentation, OpenAPI spec, or example payloads available for this endpoint.
- —The 'medical/records' path implies health data — regulatory compliance (HIPAA, GDPR) is unknown and unverified.
- —It is unclear whether record ID 34 is a real resource, a demo, or a placeholder.
- —No robots.txt or agents.txt found; no crawlable docs beyond the landing page.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/34
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/34