x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com serves medical record data behind an x402 payment wall. The specific resource `/api/v1/medical/records/17` returns JSON content upon payment of up to $0.02 in USDC on the Base network. It uses the x402 "exact" payment scheme, meaning the caller must attach a valid X-PAYMENT header with a Base USDC transaction to access the resource.
The provider's landing page advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. This particular endpoint falls under a "medical/records" path that is not explicitly listed on the homepage catalog, so its exact data contents and schema are unknown. The endpoint accepts POST requests and returns `application/json`.
Payment settles on Base (Ethereum L2) using USDC at contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The maximum amount required is 20,000 base units, which at 6 decimals equals $0.02. No API keys or rate limits are advertised. The x402 challenge was successfully captured (HTTP 402), confirming the endpoint is live.
Capabilities
Use cases
- —Retrieving medical record data on-demand with per-request USDC payment
- —Integrating health data into agent workflows without API key management
- —Programmatic access to structured medical information via x402 protocol
Fit
Best for
- —Agents or applications needing on-demand medical record lookups
- —Developers exploring x402 pay-per-call patterns on Base
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data sources
- —Bulk data retrieval where per-request pricing is inefficient
- —Users without Base USDC wallets
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/17 \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documentation for this specific medical records endpoint — no request/response schema, no description of what data is returned, and the endpoint path is not listed on the provider's homepage catalog. The medical/health data category raises regulatory concerns without any compliance information.
Warnings
- —Endpoint path /api/v1/medical/records/17 is not listed on the provider's public API catalog — its data contents are unknown.
- —Medical/health data category: no HIPAA compliance, data provenance, or regulatory information is provided.
- —No request body schema or response schema available — callers cannot know what to send or what to expect.
- —No documentation pages were accessible (pricing, README, and /api pages only showed 'Connect wallet').
- —The nature and authenticity of the 'medical records' data is entirely unverified.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring up to 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/17
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/17
- —Provider advertises $0.02 per request, no API keys, no rate limits across all endpointshttps://lowpaymentfee.com