x402basequality 0.30

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

What it does

This endpoint at `/api/v1/ehr/98` 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/98` 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 (HTTP 402) requesting payment of 20,000 base units of USDC (0x8335…2913) on the Base network, which equals $0.02 per request (USDC uses 6 decimals). Payment is made via the `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The endpoint accepts POST requests and returns `application/json`. No API key or account registration is needed — access is granted purely through the x402 payment header.

Because the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" stub with no substantive content, the actual request body format, response schema, and precise data returned by this EHR endpoint are unknown. The platform advertises uniform $0.02 pricing across all endpoints, no rate limits, and instant access via the Base network.

Capabilities

x402-paymentusdc-basepay-per-requestehr-datajson-responseno-api-keypost-method

Use cases

  • Retrieving electronic health record data for a specific resource (ID 98)
  • Integrating EHR data into health-tech applications with micropayment access
  • Agent-driven health data retrieval without pre-registration or API keys

Fit

Best for

  • Developers needing on-demand EHR data access without subscription commitments
  • AI agents that can settle x402 USDC payments on Base
  • Prototyping health data integrations with minimal setup

Not for

  • Production healthcare systems requiring HIPAA-compliant, audited data pipelines
  • Users who need detailed API documentation or guaranteed SLAs before integration
  • Applications requiring bulk or batch EHR queries at scale

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ehr/98 \
  -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 no documentation, no request/response schema, and the /ehr/98 path is not listed among the provider's advertised APIs. All doc pages return empty stubs. The actual data returned is entirely unknown.

Warnings

  • The /api/v1/ehr/98 path is not listed on the provider's landing page among advertised endpoints — its existence and purpose are unverified beyond the 402 challenge.
  • No request body schema or response schema is documented anywhere; callers must discover behavior empirically.
  • All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content.
  • EHR data may be subject to healthcare regulations (e.g., HIPAA); the provider gives no compliance information.
  • The provider site appears to be a generic x402 demo/showcase; the actual data quality and reliability behind these endpoints is unknown.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:07:09Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access