Pay-per-call medical records endpoint on Base via x402 (USDC).
What it does
This endpoint at `/api/v1/medical/records/48` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs settled via the x402 protocol on the Base network using USDC. The specific endpoint appears to serve medical record data (record ID 48) and accepts POST requests. Payment is handled inline: callers attach an X-PAYMENT header with a signed USDC payment on Base, and the server returns the requested data.
The x402 challenge confirms the endpoint is live and requires up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. The platform advertises no API keys, no rate limits, and instant access.
Important caveats: there is no documentation describing the schema of the medical records data returned, no sample responses, and no OpenAPI spec. The endpoint title "Premium API Access" is generic and does not clarify what fields or data the medical record contains. The "medical records" label raises questions about data provenance, privacy, and regulatory compliance (e.g., HIPAA). Prospective users should exercise caution and verify the nature of the data before relying on this endpoint.
Capabilities
Use cases
- —Retrieving medical record data for record ID 48 via a single paid POST request
- —Integrating pay-per-call health data access into an agent workflow
- —Testing x402 micropayment flows against a medical data endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing on-demand medical record lookups without API key management
- —Quick one-off data retrieval at low per-request cost
Not for
- —Production healthcare applications requiring HIPAA-compliant data handling
- —Bulk medical data retrieval or batch processing (no documented batch support)
- —Users who need detailed response schema documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/medical/records/48 \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) with clear pricing ($0.02 USDC on Base), but there is no OpenAPI spec, no response schema, no example data, and no documentation beyond a generic landing page. The 'medical records' label with zero schema detail and potential regulatory concerns further lower confidence.
Warnings
- —No OpenAPI or response schema available — the structure of returned medical record data is completely unknown.
- —Medical/health data category raises regulatory concerns (HIPAA, GDPR). Data provenance and compliance status are undocumented.
- —The endpoint serves a single record ID (48); it is unclear whether other record IDs are available or how records are enumerated.
- —No documentation pages returned meaningful content (pricing, README, and /api pages all just show 'Connect wallet').
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/medical/records/48
- —The platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access.https://lowpaymentfee.com
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/medical/records/48