x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/ehr/28` is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific `/ehr/28` path suggests an Electronic Health Record (EHR) resource, though the provider's landing page does not list this particular endpoint among its documented APIs. The endpoint is live and returns a valid x402 challenge on POST requests.

Payment is settled on the Base network using USDC (contract `0x8335...2913`). The `maxAmountRequired` is 20,000 base units, which at 6 decimals equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing advertised on its homepage. The x402 scheme is "exact", meaning the caller pays the precise amount per call. No API keys, rate limits, or subscriptions are required; access is granted immediately upon valid payment.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data the `/ehr/28` endpoint actually returns. The endpoint's purpose, input parameters, and output format must be discovered experimentally. Given the "EHR" path segment, this may involve sensitive health data, which warrants caution regarding regulatory compliance (HIPAA, GDPR, etc.).

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyehr-data

Use cases

  • Retrieving electronic health record data on a per-request basis
  • Integrating EHR data into agent workflows without managing API keys
  • Programmatic access to health records with crypto micropayments

Fit

Best for

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

Not for

  • Production healthcare applications requiring HIPAA-compliant audit trails and BAAs
  • Users who need detailed API documentation and guaranteed SLAs
  • Non-crypto users without Base network USDC wallets

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ehr/28 \
  -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 /api/v1/ehr/28 actually does, what inputs it accepts, or what it returns. No OpenAPI schema, no examples, and the endpoint isn't even listed on the provider's own homepage. The EHR path raises regulatory concerns with no compliance information available.

Warnings

  • The /api/v1/ehr/28 endpoint is not listed among the provider's documented APIs on the homepage — its purpose and data content are unknown.
  • EHR (Electronic Health Record) data is typically subject to HIPAA, GDPR, and other health data regulations. No compliance or privacy information is provided.
  • All documentation pages (docs, API, pricing, README) returned only a 'Connect wallet' prompt with no substantive content.
  • No request/response schema or examples are available; input parameters and output format are entirely unknown.

Citations

Provenance

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

Agent access