x402basequality 0.25

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

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

What it does

This endpoint at `/api/v1/ehr/71` 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 resource at path `/ehr/71` is labeled "Premium API Access" but its exact data domain is unclear — the "ehr" path segment suggests Electronic Health Records, though the provider's landing page does not list this endpoint among its documented categories and provides no schema or field-level documentation for it.

The endpoint is live and returns a valid x402 challenge over the Base network. Payment is settled in USDC (contract `0x8335…2913`) with a maximum amount of 20,000 base units, which at 6 decimals equals $0.02 per request. The x402 challenge specifies an `exact` payment scheme, a 300-second timeout, and accepts HTTP POST. No API key or account registration is required; callers authenticate solely via the x402 payment header.

Documentation is extremely thin. The provider's landing page lists many endpoints at $0.02 each but does not include `/api/v1/ehr/71`. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no example payloads available. Without knowing what fields to POST or what the response contains, integration requires experimentation or direct contact with the provider.

Capabilities

x402-paymentper-call-billingusdc-settlementbase-networkhttp-postno-api-keyehr-data

Use cases

  • —Retrieving health record data (EHR) on a per-request payment basis
  • —Integrating pay-per-call medical data into agent workflows
  • —Accessing premium data without API key registration

Fit

Best for

  • —Agents that can settle x402 payments in USDC on Base
  • —Use cases needing on-demand health/EHR data without subscription commitments
  • —Developers exploring x402 protocol integrations

Not for

  • —Production healthcare applications requiring documented schemas and compliance guarantees
  • —Users who cannot transact in USDC on the Base network
  • —High-volume batch retrieval where per-call pricing is inefficient

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schema, no OpenAPI spec, and the /ehr/71 path is not listed on the provider's own landing page. The purpose of the endpoint is ambiguous and cannot be verified.

Warnings

  • —The /api/v1/ehr/71 endpoint is not listed among the provider's documented APIs — its availability and purpose are unverified.
  • —'EHR' may imply Electronic Health Records, which is a regulated data category (HIPAA, etc.). No compliance information is provided.
  • —No request or response schema is available; integration requires blind experimentation.
  • —All secondary pages (docs, pricing, API, README) render only 'Connect wallet' with no useful content.

Citations

Provenance

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

Agent access

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