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/47` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs settled in USDC on the Base network. The specific resource appears to be an Electronic Health Record (EHR) endpoint, though the provider's landing page does not list it among its publicly advertised API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). The endpoint is live and returns a valid x402 challenge with a `maxAmountRequired` of 20,000 base units of USDC (6 decimals), which equals $0.02 per request — consistent with the platform's uniform pricing.

The platform advertises no API keys, no rate limits, and instant access. Payment is handled via the x402 protocol: callers include an `X-PAYMENT` header with a signed payment proof, and the server fulfills the request upon verification. The endpoint accepts POST requests and returns `application/json`. However, there is no documentation describing the request body schema, response format, or what data the EHR endpoint actually returns. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional content.

Because the endpoint path includes "ehr" (commonly associated with Electronic Health Records), this may involve health-related data. No details are available about what patient or health data is served, whether it is synthetic/sample data, or what input parameters are expected. Users should exercise caution and verify the nature of the data before integrating.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestehr-datajson-responseno-api-key

Use cases

  • Retrieving electronic health record data via a single paid API call
  • Integrating EHR data into agent workflows without managing API keys
  • Testing x402 payment protocol integrations with a low-cost endpoint

Fit

Best for

  • Developers experimenting with x402 pay-per-request protocols
  • Agents needing on-demand EHR data access without subscription commitments
  • Prototyping crypto-settled API payment flows on Base

Not for

  • Production healthcare applications requiring documented, compliant EHR APIs
  • Users who need detailed API documentation or schema guarantees
  • High-volume use cases where per-request pricing may not be economical

Quick start

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

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 schemas, no description of what the EHR endpoint returns, and the endpoint is not listed on the provider's own landing page. The docs pages are empty. This is effectively a stub listing.

Warnings

  • The /api/v1/ehr/47 endpoint is not listed among the provider's publicly advertised APIs — its purpose and data content are unknown.
  • EHR commonly refers to Electronic Health Records, which may involve regulated health data (HIPAA, etc.). The nature of the data served is undocumented.
  • No request body schema or response schema is available — callers cannot know what to send or what to expect.
  • Documentation pages (/docs, /pricing, /api, /README) all render only a 'Connect wallet' prompt with no useful content.

Citations

Provenance

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

Agent access