Pay-per-call medical records API on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 57) 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 an exact-scheme challenge requiring up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals).
The provider hosts a broader catalog of pay-per-call 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 minimum commitments. This specific endpoint falls under a "medical records" path, though the provider's landing page does not list it among its advertised categories, and no documentation, request schema, or response schema is published for it.
Because there is no OpenAPI spec, no request/response examples, and no description beyond the generic "Premium API Access" label, the actual data returned and the expected POST body are unknown. The medical records domain raises regulatory considerations (e.g., HIPAA in the US). Agents should exercise caution and verify the nature of the data before integrating.
Capabilities
Use cases
- —Retrieving medical record data for record ID 57 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
- —Agents needing on-demand medical record retrieval without subscription
- —Developers exploring x402 payment-gated API patterns
- —Scenarios where keyless, per-call billing is preferred
Not for
- —Production healthcare applications requiring HIPAA-compliant, audited data pipelines
- —Bulk retrieval of many medical records (single record ID only)
- —Users who need detailed API documentation or schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/57 \
-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). However, there is no OpenAPI spec, no request/response schema, no documentation for this specific medical records path, and the landing page doesn't even list it. The medical/health domain adds regulatory risk. Effectively a stub listing.
Warnings
- —No request or response schema available — POST body format is unknown.
- —Medical records endpoint may involve regulated health data (HIPAA, GDPR); no compliance information is provided by the provider.
- —This specific endpoint (/api/v1/medical/records/57) is not listed on the provider's landing page among advertised APIs.
- —No documentation, examples, or README content could be retrieved (pages returned only 'Connect wallet').
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/medical/records/57
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/medical/records/57
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Provider lists APIs in Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categories but does not list medical recordshttps://lowpaymentfee.com