x402basequality 0.30

Pay-per-call medical records endpoint on Base via x402, settled in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/medical/records/26

What it does

This endpoint at `/api/v1/medical/records/26` 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 protocol for payment, settling in USDC on the Base network with no API keys, no rate limits, and no subscriptions required.

The specific resource at `/api/v1/medical/records/26` is listed under the title "Premium API Access" and accepts POST requests. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD per request, since USDC uses 6 decimals). Payment is sent to the on-chain address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The response MIME type is `application/json`.

Important caveats: the endpoint path suggests it returns medical records, which is a regulated data category. No documentation, request schema, or response schema is provided beyond the x402 challenge metadata. There is no OpenAPI spec, no example payloads, and the crawled docs pages (`/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content. The nature and provenance of the medical data served is entirely unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responsemedical-records

Use cases

  • —Retrieving medical record data for record ID 26 via a single paid API call
  • —Integrating pay-per-request health data access into agent workflows
  • —Programmatic access to medical records without API key management

Fit

Best for

  • —Agents or applications needing on-demand medical record retrieval with crypto payment
  • —Developers exploring x402 pay-per-call patterns on Base

Not for

  • —Production healthcare applications requiring HIPAA-compliant, auditable data pipelines
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Bulk medical data retrieval at scale

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/medical/records/26
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 no request/response schema, no documentation, no examples, and the data category (medical records) is regulated with no information about data provenance or compliance.

Warnings

  • —Medical/health data category — may be subject to HIPAA, GDPR, or other regulations; no compliance information provided
  • —No request or response schema available; payload structure is unknown
  • —No OpenAPI spec, no documentation pages with content (all returned 'Connect wallet' only)
  • —Data provenance and authenticity of medical records is entirely unverified
  • —The endpoint path references a specific record ID (26); unclear if other IDs are available or what the data represents

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/EUKSzD
Pay-per-call medical records endpoint on Base via x402, settled in USDC. — Clawmart · Clawmart