x402basequality 0.25

x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/ehr/80

What it does

This endpoint at `/api/v1/ehr/80` is part of the lowpaymentfee.com platform, which offers a collection of x402 protocol-gated APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific endpoint being listed here appears to serve electronic health record (EHR) data, though the provider's landing page does not explicitly document the `/ehr/` path or its response schema. The endpoint is live and returns a valid x402 challenge.

Payment is settled on the Base network using USDC (contract `0x8335…2913`). The x402 challenge advertises a `maxAmountRequired` of 20,000 base units. Since USDC uses 6 decimals, this converts to $0.02 per request — consistent with the provider's stated flat pricing of $0.02/request across all endpoints. The platform advertises no API keys, no rate limits, and instant access.

Important caveats: the `/api/v1/ehr/80` path is not listed among the provider's documented API categories, and no input/output schema is available beyond the x402 challenge metadata. The crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content. The nature of the EHR data (synthetic, aggregated, or real patient data) is unknown, which raises potential regulatory concerns.

Capabilities

x402-paymentusdc-basepay-per-requestehr-datano-api-keyhttp-post

Use cases

  • —Retrieving electronic health record data on a per-request payment basis
  • —Integrating EHR data into agent workflows without managing API keys
  • —Programmatic access to health record information via x402 micropayments

Fit

Best for

  • —Agents needing on-demand EHR data with crypto micropayments
  • —Developers prototyping health data integrations without subscription commitments
  • —x402-compatible clients on the Base network

Not for

  • —Production healthcare applications requiring HIPAA-compliant, documented APIs
  • —Users who need detailed input/output schema documentation before integration
  • —Non-crypto payment workflows (no fiat option available)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ehr/80 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-header>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/ehr/80
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but the /ehr/80 path is not documented anywhere on the provider's site. No input schema, output schema, or example responses are available. Documentation pages are empty. The nature of the data served is entirely unclear, and the health-data category raises regulatory red flags.

Warnings

  • —The /api/v1/ehr/80 path is not listed among the provider's documented endpoints — it may be undocumented, experimental, or deprecated.
  • —No input or output schema is available; callers cannot know what to send or what to expect back.
  • —EHR (Electronic Health Record) data may be subject to HIPAA or other health-data regulations — the provider gives no compliance information.
  • —All documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no actual content.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 18:54:37Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/A9PDbb
x402-gated EHR endpoint on Base, pay-per-request with USDC — no API keys required. — Clawmart · Clawmart