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 lowpaymentfee.com provides premium API access to an Electronic Health Record (EHR) resource at path `/api/v1/ehr/72`. It is part of a broader platform offering dozens of x402-gated endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per request settled in USDC on the Base network.

The endpoint is live and returns a standard x402 payment challenge (HTTP 402) requiring an `X-PAYMENT` header with a payment proof. The maximum amount required is 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The timeout for payment settlement is 300 seconds.

No documentation was found describing the request body schema, expected input parameters, or the structure of the EHR response. The crawled docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no additional content. The specific nature of the EHR data (whether it is synthetic/demo data or real patient records) is unknown. Users should exercise caution given the healthcare data context and the complete absence of documentation about data provenance, compliance, or schema.

Capabilities

x402-paymentusdc-baseehr-dataper-request-billingno-api-keypay-per-use

Use cases

  • Retrieving electronic health record data for a specific resource (ID 72)
  • Integrating EHR data into agent workflows with per-call micropayments
  • Accessing health data without API key registration

Fit

Best for

  • Developers experimenting with x402 payment-gated health data APIs
  • Agents that need on-demand EHR access with crypto micropayments
  • Prototyping healthcare data integrations without subscription commitments

Not for

  • Production healthcare applications requiring HIPAA-compliant, documented APIs
  • Users who need detailed schema documentation or SLA guarantees
  • Bulk retrieval of large EHR datasets

Quick start

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

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 request/response schema, no OpenAPI spec, and no information about what EHR data is actually returned. The docs pages are empty. The healthcare context without any compliance or provenance information is a significant concern.

Warnings

  • No documentation available — all doc/pricing/API pages return only 'Connect wallet' with no content
  • No request or response schema provided; input parameters are unknown
  • EHR (Electronic Health Record) data may be subject to healthcare regulations (e.g., HIPAA); no compliance information is provided
  • Unknown whether data is synthetic/demo or real patient records
  • The specific endpoint /api/v1/ehr/72 is not listed on the provider's homepage among available APIs

Citations

Provenance

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

Agent access