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
Endpoint
https://lowpaymentfee.com/api/v1/ehr/21

What it does

This endpoint at `/api/v1/ehr/21` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific resource at path `/ehr/21` is labeled "Premium API Access" but its exact data payload is undocumented — the "ehr" path segment suggests Electronic Health Record data, though no schema or sample response is provided by the provider.

Payment is handled via the x402 protocol on the Base network. The challenge advertises a maximum amount of 20,000 base units of USDC (contract `0x8335…2913`, 6 decimals), which converts to $0.02 per request. Settlement goes to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The endpoint accepts POST requests, requires no API keys or account registration, and has a payment timeout of 300 seconds. The provider's landing page confirms a flat $0.02/request pricing model across all listed endpoints with no rate limits or minimum commitments.

Documentation is extremely sparse. The `/docs`, `/pricing`, `/api`, and `/README` pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema, and no explanation of what data the `/ehr/21` resource actually returns. The endpoint is live (returns a proper 402 challenge), but without documentation it is difficult to know what input to send or what output to expect.

Capabilities

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

Use cases

  • —Retrieving electronic health record data (resource ID 21) on a per-request payment basis
  • —Integrating health data into agent workflows without pre-registration or API keys
  • —Testing x402 micropayment flows against a live endpoint

Fit

Best for

  • —Developers experimenting with x402 pay-per-request protocols
  • —Agents needing on-demand health data access without subscription commitments
  • —Quick prototyping of crypto-settled API integrations on Base

Not for

  • —Production healthcare applications requiring documented schemas and compliance guarantees
  • —Users who need detailed API documentation or OpenAPI specs before integration
  • —Bulk data retrieval where per-request pricing would be cost-inefficient

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/ehr/21
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is zero documentation on request format, response schema, or what 'ehr/21' actually returns. The docs pages are empty. The 'ehr' path suggests health data but this is unconfirmed.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
  • —No OpenAPI spec or request/response schema provided
  • —The 'ehr' path suggests Electronic Health Record data, which may fall under regulated health data categories (HIPAA, etc.) — no compliance information is provided
  • —The specific resource '/ehr/21' is not listed on the provider's landing page among their advertised APIs
  • —Cannot verify what data is actually returned without making a paid request

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/fbLRpt
x402-gated EHR endpoint on Base, pay $0.02 per request in USDC — no API keys required. — Clawmart · Clawmart