x402basequality 0.30

x402-gated EHR data endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/ehr/12

What it does

This endpoint at `/api/v1/ehr/12` 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 endpoint appears to serve Electronic Health Record (EHR) data, though the crawled documentation provides no details about the schema, fields, or data source behind this particular resource. The platform advertises a flat $0.02 per request across all its endpoints, and the x402 challenge confirms a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02.

The platform requires no API keys and advertises no rate limits. Payment is handled entirely via the x402 protocol: callers send an `X-PAYMENT` header containing a signed payment authorization, and the server fulfills the request upon verification. The endpoint accepts POST requests and returns `application/json`. However, there is no OpenAPI spec, no request/response schema documentation, and no example payloads available from the crawled pages. The `/docs`, `/pricing`, `/api`, and `/README` pages all returned only a "Connect wallet" prompt with no substantive content.

Because the endpoint path suggests health record data (`/ehr/12`), this may involve regulated or sensitive information. The lack of documentation about what data is returned, its provenance, and any compliance considerations is a significant gap. Prospective 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 for a specific resource (ID 12)
  • —Agent-driven health data lookups with per-request crypto payment
  • —Integrating EHR data into workflows without subscription or API key management

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, audited data pipelines
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Anyone unable to transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the docs pages are empty. The nature of the EHR data is entirely undocumented, raising both usability and compliance concerns.

Warnings

  • —No request or response schema documentation available — input/output formats are unknown
  • —Endpoint path suggests Electronic Health Record data, which may be subject to HIPAA or other health data regulations; no compliance information is provided
  • —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no content
  • —The specific resource '/ehr/12' is undocumented; it is unclear what entity ID 12 represents or whether other IDs are available

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/kBN3ex
x402-gated EHR data endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart