Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/71` 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. Each call is settled on the Base network using USDC (contract `0x8335…2913`) through the x402 exact-payment scheme. The specific endpoint probed here serves medical records (record ID 71), accepting POST requests and returning `application/json` responses.
The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. USDC uses 6 decimals, so the per-request cost is $0.02 — consistent with the site's uniform $0.02/request pricing across all listed endpoints. No API keys or rate limits are advertised; access is granted immediately upon valid payment. The payment timeout is 300 seconds.
Important caveats: the endpoint is labeled "medical records," which places it in a regulated data category, yet no documentation exists describing the data schema, provenance, compliance posture (HIPAA, GDPR), or what record ID 71 actually contains. The site's /api, /pricing, and /README pages all resolve to a minimal "Connect wallet" stub with no further documentation. There is no OpenAPI spec, no example request/response, and no description of input parameters. Treat this endpoint with caution until the provider publishes proper documentation and compliance disclosures.
Capabilities
Use cases
- —Retrieving medical record data on a per-request payment basis
- —Integrating health records into agent workflows that can settle USDC on Base
- —Programmatic access to structured medical data without API key provisioning
Fit
Best for
- —Agents or applications that need on-demand medical record access with crypto micropayments
- —Developers exploring x402 payment flows on Base
- —Use cases where keyless, pay-per-call access is preferred over subscription billing
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Users who need detailed API documentation, schemas, or compliance guarantees before integration
- —High-volume batch retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/71 \
-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 USDC on Base), but there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and no compliance information for what is labeled as medical data. The site's doc pages are empty stubs.
Warnings
- —Endpoint is categorized as 'medical records' — a regulated data category — but no compliance disclosures (HIPAA, GDPR, etc.) are provided.
- —No API documentation, OpenAPI spec, or example request/response is available anywhere on the site.
- —The /api, /pricing, and /README pages all return only a 'Connect wallet' stub with no useful content.
- —The nature and provenance of the data behind record ID 71 is completely unknown.
- —Input parameters for the POST request are undocumented.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/71
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/71
- —Site advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The /api, /pricing, and /README pages contain only a 'Connect wallet' stubhttps://lowpaymentfee.com/api