Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at `/api/v1/medical/records/58` is part of the lowpaymentfee.com platform, which hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. The specific endpoint being listed appears to serve medical record data (record ID 58). Payment is settled on the Base network using USDC (contract `0x8335…2913`) through the x402 exact-payment scheme. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD — consistent with the site's uniform $0.02/request pricing across all endpoints.
The endpoint accepts HTTP POST requests and returns `application/json` responses. No API keys or rate limits are advertised; access is gated entirely by the x402 payment header. The payment timeout is 300 seconds (5 minutes). No OpenAPI schema, request body specification, or response body schema was found in the probe or crawl material, so the exact fields accepted and returned are unknown.
Note: This endpoint is categorized under medical records, which may involve regulated health data. No documentation was found describing the nature, source, or compliance posture of the data served. Consumers should exercise caution and verify regulatory compliance (e.g., HIPAA) before integrating.
Capabilities
Use cases
- —Retrieving medical record data for record ID 58 on a per-call payment basis
- —Integrating health data into agent workflows without pre-registration or API keys
- —Demonstrating x402 micropayment flows for data access
Fit
Best for
- —Agents needing on-demand medical record access without subscription commitments
- —Developers experimenting with x402 payment-gated data APIs
- —Low-volume, pay-as-you-go health data retrieval
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk medical record retrieval or batch processing at scale
- —Use cases requiring documented request/response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/58 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response documentation, no description of what data is actually returned, and the medical records domain raises regulatory concerns with zero compliance documentation. Effectively a stub listing.
Warnings
- —No request or response schema documented — consumers cannot know what fields to send or expect back.
- —Endpoint serves 'medical records' data with no documentation on data source, accuracy, or regulatory compliance (e.g., HIPAA).
- —The specific record ID (58) is hardcoded in the URL; it is unclear whether other record IDs are available or how to discover them.
- —No robots.txt or agents.txt found; no OpenAPI spec available.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, requiring USDC payment on Base network with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/medical/records/58
- —The site advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/58