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

What it does

This endpoint at `/api/v1/ehr/36` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs settled on the Base network using USDC. The specific resource at path `/ehr/36` is labeled "Premium API Access" in the x402 challenge but its exact data payload is undocumented — the "ehr" path segment suggests Electronic Health Records, though no schema or sample response is provided by the provider.

The endpoint is live and returns a valid x402 challenge (HTTP 402) requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site-wide $0.02/request pricing advertised on the landing page. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The endpoint accepts POST requests.

The broader lowpaymentfee.com platform advertises APIs across data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, gas estimates), and infrastructure (geocoding, validation, conversion). All share the same $0.02 pricing and x402 payment model with no API keys, no rate limits, and instant access. However, documentation beyond the landing page is essentially empty (all doc pages just show "Connect wallet"), so the actual request/response schemas for this and other endpoints are unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestehr-datapost-endpointno-api-key

Use cases

  • Retrieving electronic health record data (resource ID 36) on a per-request payment basis
  • Integrating EHR lookups into agent workflows without managing API keys or subscriptions
  • Paying for health data access with USDC on Base via the x402 protocol

Fit

Best for

  • Developers or agents needing on-demand EHR data without subscription commitments
  • x402-native agent pipelines that settle payments in USDC on Base
  • Prototyping pay-per-call health data integrations

Not for

  • Production healthcare systems requiring documented schemas, SLAs, and compliance guarantees
  • Users who need bulk or batch EHR data retrieval at scale
  • Anyone requiring HIPAA-compliant audit trails or data provenance documentation

Quick start

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

Endpoint

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 what the EHR endpoint actually returns — no request schema, no response schema, no examples. All doc/pricing/README pages are empty beyond a wallet-connect prompt. The 'ehr' path suggests health data but this is unconfirmed. Effectively a stub listing.

Warnings

  • No documentation exists for this endpoint — all doc pages return only 'Connect wallet'
  • The 'ehr' path suggests Electronic Health Records, which is a regulated data category (HIPAA, GDPR); no compliance or privacy information is provided
  • No request or response schema is available; the actual data returned is unknown
  • The provider site offers dozens of endpoints at $0.02 each across very different domains (AI, finance, geocoding, EHR) with no documentation — exercise caution regarding data quality and legitimacy

Citations

Provenance

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

Agent access