Pay-per-call medical records endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves medical record data (specifically record ID 52) behind a micropayment wall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per request on the Base network. This particular endpoint falls under a "medical records" path, but no documentation exists describing the schema of the returned medical record data, what fields are included, or whether the record ID is parameterized. The crawled pages beyond the landing page (including /api, /pricing, and /README) returned only a "Connect wallet" prompt with no additional documentation.
Because there is no OpenAPI spec, no response schema, and no description of what the medical record payload actually contains, this listing carries significant uncertainty. The endpoint is confirmed live (returns a proper 402 x402 challenge), but consumers should be aware that the "medical records" framing is unverified — there is no way to confirm the nature or quality of the data without making a paid request.
Capabilities
Use cases
- —Retrieving medical record data (record 52) via a single paid POST request
- —Demonstrating x402 micropayment integration on the Base network
- —Agent-driven data retrieval with no authentication beyond payment
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents that need to fetch data behind micropayment walls on Base
- —Testing pay-per-call patterns with low-cost USDC transactions
Not for
- —Production healthcare applications requiring verified, HIPAA-compliant data sources
- —Bulk retrieval of multiple medical records (only record 52 is documented)
- —Users who need detailed API documentation or response schema before purchasing
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/52 \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and network details. However, there is zero documentation on the request body, response schema, or what 'medical records' data is actually returned. The crawled pages provide no additional detail beyond the landing page catalog. The medical/health framing without any verifiable documentation is a significant concern.
Warnings
- —No OpenAPI spec or response schema available — the structure of the returned medical record data is completely unknown.
- —The 'medical records' label is unverified; there is no documentation confirming the nature, source, or accuracy of the data.
- —Medical/health data may be subject to regulatory requirements (HIPAA, GDPR) — no compliance information is provided by the endpoint operator.
- —Only record ID 52 is referenced; it is unclear whether other record IDs are available or what they represent.
- —Pages at /api, /pricing, and /README returned no useful content (only 'Connect wallet').
Citations
- —Endpoint returns a valid x402 challenge with status 402 and x402Version 1https://lowpaymentfee.com/api/v1/medical/records/52
- —Payment is in USDC on Base network, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/medical/records/52
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/52
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com