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 x402-enabled endpoint at lowpaymentfee.com provides access to a medical records resource (`/api/v1/medical/records/45`) via POST requests, paid per-call in USDC on the Base network. The endpoint returns a 402 challenge advertising a maximum cost of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals), consistent with the provider's site-wide flat pricing of $0.02 per request.

The provider, lowpaymentfee.com, hosts a broad catalog of x402 pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all at the same $0.02/request price point. No API keys are required; payment is handled inline via the x402 protocol's X-PAYMENT header. The site advertises no rate limits and instant access.

Important caveat: this specific endpoint is labeled "medical/records," which implies it handles health-related data. No documentation, OpenAPI schema, request/response examples, or privacy disclosures were found in the crawl. The actual data returned by this endpoint is unknown — it could be synthetic/demo data or real medical records. Agents and developers should exercise caution given the sensitive nature of medical data and the complete absence of documentation about what this endpoint actually returns.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-callmedical-recordspost-endpointno-api-key

Use cases

  • Retrieving medical record data for record ID 45 via a single paid POST request
  • Demonstrating x402 payment protocol integration with a medical data endpoint
  • Programmatic access to health records without pre-registration or API keys

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents needing pay-per-call access to medical data without subscription commitments
  • Testing x402 integration flows with low-cost endpoints

Not for

  • Production healthcare applications requiring HIPAA compliance guarantees
  • Use cases needing documented request/response schemas and SLAs
  • Bulk medical data retrieval (pay-per-call at $0.02 adds up)

Quick start

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

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). However, there is zero documentation on request format, response schema, or what data is actually returned. The medical records domain raises regulatory concerns with no privacy or compliance information available. No OpenAPI spec, no examples, and crawled pages beyond the homepage returned only 'Connect wallet' with no useful content.

Warnings

  • Medical/health data endpoint with no documentation on data provenance, privacy policy, or regulatory compliance (e.g., HIPAA).
  • No request or response schema available — unknown what POST body is expected or what data is returned.
  • No OpenAPI specification found for any endpoints on this provider.
  • The specific record ID '45' is hardcoded in the URL; unclear if this is a demo resource or real patient data.
  • Provider site pages (/api, /pricing, /README) returned no useful content beyond 'Connect wallet'.

Citations

Provenance

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

Agent access