x402basequality 0.25

x402-gated premium API access 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 a collection of pay-per-call APIs gated via the x402 protocol on the Base network. The specific endpoint `/api/v1/ehr/48` is listed under "Premium API Access" and accepts POST requests, settling payments in USDC (contract 0x8335…2913 on Base). The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys, rate limits, or upfront commitments are needed — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The broader lowpaymentfee.com platform advertises multiple API categories at the same $0.02/request price point: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). However, the specific endpoint `/api/v1/ehr/48` does not clearly map to any of these advertised categories — the "ehr" path segment suggests Electronic Health Records, but no documentation confirms what data or functionality this particular endpoint returns.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawled material. The endpoint is confirmed live (returns a proper 402 challenge), but the actual payload format and response structure remain unknown.

Capabilities

x402-paymentper-request-billingusdc-settlementbase-networkpost-endpointno-api-keyno-rate-limit

Use cases

  • Accessing premium data behind a per-request paywall without needing API keys
  • Programmatic pay-per-call access to health or data endpoints via x402
  • Agent-driven workflows that need instant, keyless API access settled in USDC on Base

Fit

Best for

  • Developers or agents wanting zero-signup, pay-as-you-go API access
  • x402-compatible wallets and agent frameworks on Base
  • Low-volume or exploratory use cases where $0.02/request is acceptable

Not for

  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • High-volume production workloads where per-request crypto settlement adds overhead
  • Anyone requiring non-crypto payment methods

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/ehr/48 \
  -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 no documentation, no OpenAPI schema, no request/response examples, and the purpose of the /ehr/48 path is unexplained. Effectively a stub listing.

Warnings

  • The /ehr/48 path suggests Electronic Health Records data, which may fall under regulated health data categories (HIPAA, etc.) — no compliance information is provided.
  • No documentation is available: /docs, /pricing, /api, and /README all return only a wallet-connect prompt.
  • No request body schema or response schema is documented; callers cannot know what to send or what to expect.
  • The specific function of this endpoint is unclear — 'Premium API Access' is a generic label.

Citations

Provenance

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

Agent access