Pay-per-call medical records endpoint on Base via x402 (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/15`) 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 cost of $0.02 per request (20,000 base units at 6 decimals).
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 with no API keys, no rate limits, and no minimum commitments. However, the specific medical records endpoint being listed here has no public documentation beyond its x402 challenge. There is no OpenAPI spec, no request/response schema, and no description of what data is returned or what input the POST body expects.
Because this endpoint falls in the medical/health data category and lacks any documentation about data provenance, compliance, or content, users should exercise caution. The endpoint is confirmed live (returns a valid 402 challenge), but the absence of schema details and the sensitive nature of medical data are significant concerns.
Capabilities
Use cases
- —Retrieving medical record data for record ID 15 via a single paid API call
- —Integrating pay-per-call health data access into agent workflows
- —Demonstrating x402 micropayment protocol usage for sensitive data endpoints
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record retrieval without API key management
- —Low-volume, pay-as-you-go access to health data
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk medical data retrieval or high-throughput health analytics
- —Users who need documented request/response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/15 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and network. However, there is zero documentation on request format, response schema, or what medical data is actually served. The medical/health category raises regulatory concerns with no compliance information available.
Warnings
- —No OpenAPI spec or request/response schema available for this endpoint
- —Medical/health data category — no information on HIPAA compliance, data provenance, or regulatory status
- —The specific record ID (15) is hardcoded in the URL; unclear if other record IDs are accessible or what they represent
- —No documentation beyond the x402 challenge and the provider's generic landing page
- —Provider landing page lists many API categories at $0.02 each but provides no detailed docs for any of them
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base, maxAmountRequired 20000 (=$0.02)https://lowpaymentfee.com/api/v1/medical/records/15
- —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/15