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 paywall. The specific resource `/api/v1/medical/records/51` returns JSON content upon payment of up to $0.02 in USDC on the Base network. It is part of a broader platform (lowpaymentfee.com) that offers 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 via x402 with no API keys, no rate limits, and no subscriptions required.
The x402 challenge was successfully captured, confirming the endpoint is live. It accepts POST requests, requires an X-PAYMENT header, and settles payments to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02.
Important caveats: the endpoint is labeled "medical/records" but no documentation exists describing the schema, fields, or nature of the data returned. The crawled site pages beyond the landing page returned only "Connect wallet" with no further docs, README, or OpenAPI spec. It is unclear whether this returns real medical data, synthetic/demo data, or placeholder content. Users should exercise caution given the sensitive nature of medical data and the complete absence of documentation about data provenance, compliance, or content structure.
Capabilities
Use cases
- —Retrieving medical record data via a single pay-per-call request
- —Testing x402 payment flows against a live endpoint on Base
- —Programmatic access to record #51 without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need keyless, pay-per-use API access
- —Quick one-off data retrieval without subscription overhead
Not for
- —Production healthcare applications requiring HIPAA compliance documentation
- —Use cases needing bulk medical record retrieval or search
- —Anyone requiring verified, auditable medical data provenance
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/51 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation about what the endpoint actually returns — no OpenAPI spec, no response schema, no examples. The medical records label raises compliance and data-provenance questions that are entirely unaddressed. Effectively a stub listing.
Warnings
- —No documentation exists for this endpoint — response schema, fields, and data content are completely unknown.
- —Endpoint is labeled 'medical/records' but there is no information about data provenance, whether data is real or synthetic, or any compliance certifications (e.g., HIPAA).
- —The /api, /pricing, and /README pages all returned only 'Connect wallet' with no useful content.
- —No OpenAPI spec or ai-plugin manifest was found.
- —Regulated data category (medical/health) — exercise extreme caution.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/medical/records/51
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/51
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The site lists multiple API categories including Data & Analytics, AI & ML, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com