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 69) 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, 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 falls under a "medical/records" path, but no documentation exists describing the request body schema, the fields returned, or the nature of the medical data served. The existing description is simply "Premium API Access," which is generic and uninformative.
Because there is no OpenAPI spec, no request/response examples, and no documentation beyond the landing page listing, the actual behavior of this endpoint is unknown. The endpoint is confirmed live (returns a proper 402 x402 challenge), but callers should exercise caution given the medical data category and the complete absence of documentation about data provenance, compliance, or content.
Capabilities
Use cases
- —Retrieving medical record data for record ID 69 via a single paid API call
- —Integrating pay-per-use 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 retrieval without API key management
- —Prototyping pay-per-call data access patterns
Not for
- —Production healthcare applications requiring HIPAA compliance documentation
- —Use cases needing bulk medical record retrieval or batch processing
- —Callers who need detailed API documentation or request/response schemas before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/69 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 x402 challenge, but there is zero documentation on request format, response schema, or the nature of the medical data. No OpenAPI spec, no examples, and the medical data category raises regulatory concerns with no compliance information provided.
Warnings
- —No API documentation, OpenAPI spec, or request/response schema available
- —Endpoint serves 'medical/records' data with no information about data provenance, accuracy, or regulatory compliance (e.g., HIPAA)
- —The specific record ID (69) is hardcoded in the path — unclear if other IDs are available or what the data represents
- —No information about what POST body (if any) is expected
Citations
- —Endpoint returns a valid x402 challenge with USDC on Base network at maxAmountRequired 20000 (=$0.02)https://lowpaymentfee.com/api/v1/medical/records/69
- —Provider advertises $0.02 per request, no API keys, no rate limits, Base network settlementhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/69