x402basequality 0.30

x402-gated premium API endpoint on Base, pay-per-request with USDC.

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

What it does

This endpoint at `/api/v1/ehr/87` is part of the lowpaymentfee.com platform, a collection of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services. The specific endpoint is labeled "Premium API Access" and accepts POST requests, returning JSON responses. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 exact-payment scheme.

The x402 challenge indicates a maximum amount of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all endpoints, with no API keys, no rate limits, and no minimum commitments required. The endpoint is live and returns a proper 402 challenge.

Important caveat: the specific functionality behind `/api/v1/ehr/87` is not documented anywhere in the crawled material. The path segment "ehr" could suggest electronic health records, but this is speculative — the platform's landing page does not list this endpoint among its published API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure). Without documentation or example request/response payloads, the actual data returned by this endpoint is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responsepost-method

Use cases

  • —Accessing premium data behind a per-request paywall without API key registration
  • —Agent-driven programmatic data retrieval with automatic USDC micropayments
  • —Integrating pay-as-you-go API calls into Web3-native workflows

Fit

Best for

  • —Developers wanting zero-signup, pay-per-call API access
  • —AI agents with x402-compatible payment capabilities on Base
  • —Users who prefer crypto micropayments over subscription billing

Not for

  • —Users needing detailed documentation or schema definitions before integration
  • —Applications requiring free or subscription-based access models
  • —Use cases where the specific data contract must be known upfront

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what /api/v1/ehr/87 actually does. No request schema, no response schema, no examples, and the endpoint is not listed on the provider's own landing page. The functionality is entirely opaque.

Warnings

  • —The endpoint /api/v1/ehr/87 is not listed among the provider's published APIs — its purpose and data contract are unknown.
  • —The path segment 'ehr' may refer to electronic health records, which could involve regulated health data (HIPAA, etc.). Exercise caution.
  • —No request or response schema is available; callers cannot know what to send or what to expect back.
  • —Documentation pages (/docs, /api, /pricing, /README) all returned only a 'Connect wallet' prompt with no actual content.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/qTvvgB
x402-gated premium API endpoint on Base, pay-per-request with USDC. — Clawmart · Clawmart