Pay-per-call medical records API on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 19) 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 endpoint is live and returns a proper 402 challenge, confirming it is operational.
Because there is no OpenAPI spec, no request/response examples, and no documentation beyond the landing page listing, the actual content and utility of this endpoint remain unclear. The "medical/records" path raises questions about data provenance and regulatory compliance (e.g., HIPAA) that are not addressed anywhere in the available materials. Prospective users should exercise caution and verify the nature of the data before relying on this endpoint.
Capabilities
Use cases
- —Retrieving medical record data on a per-call basis without subscription
- —Integrating health data into agent workflows with micropayments
- —Testing x402 payment flows against a live endpoint
Fit
Best for
- —Developers exploring x402 payment protocol integrations
- —Agents needing on-demand medical record lookups with crypto micropayments
- —Prototyping pay-per-call data access patterns on Base
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling
- —Users needing detailed API documentation or schema guarantees
- —High-volume batch retrieval of medical records
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/19 \
-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/response schemas, no OpenAPI spec, and the medical records domain raises regulatory concerns that are completely unaddressed. Effectively a stub listing.
Warnings
- —No API documentation, OpenAPI spec, or request/response schema available
- —Medical records endpoint with no information about data provenance, consent, or regulatory compliance (e.g., HIPAA)
- —No example responses or field descriptions — actual content of the endpoint is unknown
- —The provider site shows many endpoints but all non-root pages returned only 'Connect wallet' with no useful content
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base network at maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/medical/records/19
- —Provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/19