Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 49) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum amount 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 site (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 specific endpoint falls under a "medical records" path, but no documentation, schema, or sample response is available beyond the x402 challenge itself. The exact structure of the request body and the fields returned in the response are unknown.
Because this endpoint deals with medical records, consumers should be aware of potential regulatory implications (e.g., HIPAA in the US, GDPR in the EU). The lack of documentation about what data is returned, how it is sourced, and what privacy safeguards are in place is a significant concern. No OpenAPI spec, README, or detailed docs were found during crawling.
Capabilities
Use cases
- —Retrieving medical record data for record ID 49 via a single paid API call
- —Integrating pay-per-call health data into agent workflows without API key management
- —Demonstrating x402 payment protocol usage on the Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record access without subscription commitments
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk medical records retrieval or high-throughput use cases
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/49 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no OpenAPI spec, no request/response schema, no documentation, and no sample data. The medical records domain raises regulatory red flags. Effectively a stub listing.
Warnings
- —No API documentation, OpenAPI spec, or response schema available — request/response structure is entirely unknown.
- —Endpoint serves medical records: potential HIPAA/GDPR regulatory concerns. No information on data sourcing, privacy, or compliance.
- —Only a single record ID (49) is referenced; unclear if other IDs are valid or what the data represents.
- —The provider site shows many endpoints but detailed docs pages (/api, /pricing, /README) returned only a 'Connect wallet' prompt with no content.
Citations
- —Endpoint returns a 402 x402 challenge with USDC on Base, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/medical/records/49
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/medical/records/49