Pay-per-call medical records endpoint on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 75) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 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. This specific endpoint sits under the /api/v1/medical/records path, but the crawled landing page does not list a "medical" category or document the schema of the records returned. There is no OpenAPI spec, no request/response examples, and no documentation beyond the x402 challenge itself. The endpoint is live (returns a well-formed 402 challenge), but the actual data content and input parameters are unknown.
Because this endpoint deals with medical records, consumers should exercise caution regarding data provenance, accuracy, and regulatory compliance (e.g., HIPAA in the US). The lack of documentation makes it impossible to verify what data is returned or whether it contains real patient information.
Capabilities
Use cases
- —Retrieving medical record data for record ID 75 via a single paid API call
- —Integrating pay-per-call medical data access into agent workflows
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record lookups without API key management
- —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 schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/75 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request parameters, response schema, or the nature of the medical records data. The landing page does not even list a medical category. This is effectively a stub listing with significant unknowns, especially concerning given the regulated data category.
Warnings
- —No API documentation, OpenAPI spec, or request/response examples available
- —Endpoint serves 'medical records' — potential regulatory concerns (HIPAA, GDPR) with no compliance information provided
- —The provider's landing page does not list a medical records category, raising questions about data provenance and legitimacy
- —Response schema is completely unknown; callers cannot verify what data will be returned
- —Only a single record ID (75) is referenced; unclear if other IDs are valid or what the data represents
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base network, maxAmountRequired 20000https://lowpaymentfee.com/api/v1/medical/records/75
- —Provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/75