x402basequality 0.30

Pay-per-call medical records endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/medical/records/59` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific resource at `/medical/records/59` is listed under the provider's generic "Premium API Access" label; no further documentation describes the schema or semantics of the medical records data returned.

The x402 challenge confirms the endpoint is live and accepts POST requests. The `maxAmountRequired` is 20,000 base units of USDC (6 decimals), which equals $0.02 per request — consistent with the site-wide flat pricing advertised on the landing page. Payment is sent to `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout. No API keys or rate limits are required; access is gated entirely by the x402 micropayment.

Important caveats: there is no OpenAPI schema, no request/response documentation, and no explanation of what "medical records" data is actually served. The endpoint path suggests health-related data, which may carry regulatory implications (HIPAA, GDPR). Prospective consumers should verify data provenance and compliance before integrating.

Capabilities

x402-paymentusdc-basepay-per-requestmedical-recordspost-endpointno-api-keymicropayment

Use cases

  • Retrieving medical record data on a per-request payment basis
  • Integrating health data into agent workflows without subscription overhead
  • Testing x402 micropayment flows against a live endpoint

Fit

Best for

  • Developers exploring x402 pay-per-call patterns
  • Agents needing on-demand data access without API key management
  • Low-volume consumers who prefer per-request billing over subscriptions

Not for

  • Production healthcare applications requiring verified, HIPAA-compliant data sources
  • High-throughput bulk data retrieval where per-request pricing is inefficient
  • Users who need detailed API documentation or guaranteed SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/59 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request parameters, response schema, or what medical records data is actually returned. No OpenAPI spec, no examples, and the health-data category raises regulatory concerns with no compliance information provided.

Warnings

  • No request or response schema documentation available
  • Endpoint serves 'medical records' data with no stated compliance (HIPAA, GDPR, etc.) — verify data provenance before use
  • The provider site offers many endpoint categories but individual endpoint docs are absent
  • The specific record ID '59' in the path is unexplained — unclear if this is a fixed demo or parameterized resource

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 22:48:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access