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 lowpaymentfee.com serves medical record data (specifically record ID 82) 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. This particular endpoint falls under a "medical records" path, though no documentation beyond the landing page and the x402 challenge is available. There is no OpenAPI spec, no detailed schema for the request body or response, and no sample payloads. The exact nature of the medical data returned (synthetic, demo, or real) is unknown from the available material.
Because the endpoint path references medical records, consumers should exercise caution regarding data provenance, regulatory compliance (HIPAA, GDPR), and whether the data is real patient information or synthetic/demo data. The lack of documentation makes it impossible to verify this from the crawl alone.
Capabilities
Use cases
- —Retrieving medical record data on a per-call payment basis
- —Integrating health data into agent workflows without subscription commitments
- —Demonstrating x402 micropayment flows with a medical data endpoint
Fit
Best for
- —Agents needing on-demand medical record lookups without API key management
- —Developers exploring x402 payment protocol integrations
- —Low-volume, pay-as-you-go health data consumers
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —High-volume bulk medical data retrieval (no documented batch support)
- —Users who need detailed API documentation or response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/82 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation for the medical records resource, and no examples. The medical data category raises regulatory concerns that are unaddressed.
Warnings
- —No OpenAPI spec or request/response schema available
- —Medical records endpoint with no documentation on data provenance, compliance, or whether data is real or synthetic
- —Potential HIPAA/GDPR regulatory concerns — use with caution
- —Only record ID 82 is referenced; unclear if other IDs are valid or what the data model looks like
- —No robots.txt or agents.txt present
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/82
- —Provider lists all APIs at $0.02/request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/82