x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/ehr/3` is part of the lowpaymentfee.com platform, which offers a broad catalog of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific `/api/v1/ehr/3` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its advertised categories, and no documentation describes its request or response schema.

The endpoint is live and returns a valid x402 challenge over the Base network. Payment is settled in USDC (contract `0x8335…2913`) with a max amount of 20,000 base units, which at 6 decimals equals $0.02 per request. The platform advertises a uniform $0.02/request pricing across all endpoints, no API keys, no rate limits, and instant access. The x402 challenge specifies a POST method and a 300-second payment timeout.

Because the crawled docs pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, there is no schema documentation, example payloads, or detailed description of what this EHR endpoint actually returns. Consumers should treat this as an exploratory endpoint until the provider publishes proper documentation.

Capabilities

x402-paymentpay-per-requestusdc-settlementbase-networkehr-datapost-methodno-api-key

Use cases

  • Retrieving electronic health record data on a per-request payment basis
  • Integrating EHR lookups into agent workflows without managing API keys
  • Programmatic access to health record resources settled via USDC on Base

Fit

Best for

  • Developers needing keyless, pay-per-call EHR data access
  • AI agents that can settle x402 micropayments on Base
  • Prototyping health-data integrations without subscription commitments

Not for

  • Production healthcare systems requiring HIPAA-compliant, documented APIs with SLAs
  • Users who need detailed schema documentation before integrating
  • High-volume batch EHR queries where per-request pricing is inefficient

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schema, no examples, and the specific /ehr/3 path is not even listed on the provider's landing page. Docs pages are empty. The endpoint's purpose and data format are entirely unknown.

Warnings

  • The /api/v1/ehr/3 endpoint is not listed among the provider's advertised APIs on the landing page — its existence and purpose are unverified beyond the 402 challenge.
  • No request or response schema documentation exists; all docs pages return only a 'Connect wallet' prompt.
  • EHR (Electronic Health Record) data may be subject to HIPAA and other health-data regulations — the provider gives no compliance or privacy information.
  • The provider's documentation infrastructure appears non-functional or gated behind wallet connection.

Citations

Provenance

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

Agent access