x402-gated medical records endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/100`) behind an x402 paywall. The endpoint is live and returns a standard x402 challenge when called without payment. Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) with the "exact" scheme. The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). The endpoint accepts HTTP POST requests and returns `application/json`.
The provider, lowpaymentfee.com, hosts a broad catalog of x402-gated APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This specific endpoint falls under a "medical records" path, but no documentation, schema, or sample payloads are available to clarify what data is returned or what input fields are expected. The provider's landing page does not list this medical records endpoint among its advertised APIs, so its exact functionality and data source are unclear.
Because there is no OpenAPI spec, no request/response schema beyond the x402 challenge metadata, and no documentation describing the medical records resource, consumers should treat this endpoint with caution. The "medical" category also raises regulatory considerations (HIPAA, data privacy) that are not addressed anywhere in the available materials.
Capabilities
Use cases
- —Retrieving medical record data for record ID 100 via a single paid API call
- —Integrating pay-per-request health data access into agent workflows
- —Demonstrating x402 micropayment protocol usage on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record lookups without API key management
- —Prototyping pay-per-call healthcare data integrations
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Use cases needing bulk or batch medical record retrieval at scale
- —Anyone requiring detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/100 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, no examples, and the medical records endpoint is not even listed on the provider's own landing page. The health/medical category raises regulatory concerns with zero compliance information available.
Warnings
- —No API documentation or OpenAPI spec available for this endpoint.
- —No request body schema or response schema provided — consumers cannot know what to send or what they will receive.
- —This endpoint is in the 'medical records' category, which may be subject to HIPAA and other health data regulations; no compliance information is provided.
- —This specific endpoint (/api/v1/medical/records/100) is not listed among the provider's advertised APIs on the landing page.
- —The hardcoded record ID '100' in the path suggests this may be a demo or placeholder resource.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base network.https://lowpaymentfee.com/api/v1/medical/records/100
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/100
- —The provider advertises $0.02 per request, no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The medical records endpoint is not listed among the provider's advertised API categories on the landing page.https://lowpaymentfee.com