x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific medical record (record ID 22) behind an x402 payment wall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The provider's landing page lists a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, infrastructure utilities, and more — all priced at $0.02 per request. This particular endpoint falls under a "medical/records" path, but no documentation, request schema, or response schema is published for it. The landing page does not mention a medical records category at all, so the purpose and data returned by this specific route are unclear.
Because no OpenAPI spec, request body schema, or example responses are available, agents calling this endpoint will need to discover the expected input format experimentally. The endpoint is confirmed live (returns a valid x402 402 challenge). No API keys or rate limits are advertised.
Capabilities
Use cases
- —Retrieving a specific medical record (ID 22) via programmatic pay-per-call access
- —Demonstrating x402 payment flows against a live endpoint on Base
- —Integrating USDC micropayments into agent workflows that need medical data
Fit
Best for
- —Agents or developers exploring x402 payment protocol integrations
- —Programmatic access to medical record data without API key registration
- —Micropayment-gated data retrieval on Base L2
Not for
- —Production healthcare applications requiring HIPAA-compliant, documented APIs
- —Bulk retrieval of many medical records (only record 22 is addressed by this endpoint)
- —Users who need detailed request/response documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/22 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and the medical records category is not even listed on the provider's own landing page. The actual data returned is completely unknown, making this effectively a stub listing.
Warnings
- —No documentation or schema available for the /api/v1/medical/records/22 endpoint.
- —The provider's landing page does not list any medical records endpoints — this path may be a placeholder or test route.
- —Medical/health data may be subject to regulatory requirements (e.g., HIPAA); no compliance information is provided.
- —No example request or response bodies are available; input format must be discovered experimentally.
- —The endpoint serves a single record ID (22); scope and utility are unclear.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Base network.https://lowpaymentfee.com/api/v1/medical/records/22
- —The provider lists APIs at $0.02 per request across data, AI, finance, and infrastructure categories, with no API keys or rate limits.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/22