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/60

What it does

This endpoint at `/api/v1/ehr/60` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific `/ehr/60` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not explicitly list or document this particular endpoint. The platform advertises a uniform $0.02 per request pricing model across its API catalog.

The endpoint is live and returns a valid x402 challenge on POST. Payment is settled in USDC on the Base network (asset `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) using the "exact" scheme. The `maxAmountRequired` is 20000 base units, which at 6 decimals equals $0.02 — consistent with the site-wide pricing. No API keys, rate limits, or subscriptions are required; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.

Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the `/ehr/60` endpoint actually returns. The "EHR" path segment and the number 60 are not explained anywhere in the crawled material. Callers should treat this as an exploratory endpoint until the provider publishes proper documentation.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyehr-data

Use cases

  • —Retrieving electronic health record data on a per-request basis
  • —Integrating EHR lookups into agent workflows without managing API keys
  • —Programmatic access to health-related data records via crypto micropayments

Fit

Best for

  • —Developers experimenting with x402 pay-per-call protocols
  • —Agents needing on-demand EHR data without subscription overhead
  • —Projects already using USDC on Base for micropayments

Not for

  • —Production healthcare applications requiring documented, HIPAA-compliant APIs
  • —Users who need detailed schema documentation before integrating
  • —High-volume bulk EHR data retrieval (no documented batch support)

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is zero documentation for this specific endpoint — no schema, no examples, no explanation of what 'ehr/60' returns. The docs pages are empty. The endpoint path is not even listed on the provider's landing page, making this effectively a stub listing.

Warnings

  • —The /api/v1/ehr/60 endpoint is not listed on the provider's landing page among available APIs.
  • —No documentation exists for this endpoint — docs, pricing, API, and README pages all show only 'Connect wallet'.
  • —'EHR' typically refers to Electronic Health Records, which may involve regulated health data (HIPAA, GDPR). No compliance information is provided.
  • —No request or response schema is available; callers cannot know what to send or what to expect back.

Citations

Provenance

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

Agent access

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