x402basequality 0.30

x402-gated account balance endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/accounts/72/balance

What it does

This endpoint at lowpaymentfee.com provides a "Premium API Access" resource at `/api/v1/accounts/72/balance`, gated behind the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access via x402 on the Base network.

However, the specific endpoint being listed here (`/api/v1/accounts/72/balance`) is not explicitly documented on the site's landing page among the advertised APIs. Its purpose — presumably returning an account balance — is inferred from the URL path. No request/response schema, documentation, or examples are available beyond the x402 challenge metadata. The docs, pricing, API, and README pages all resolve to a minimal "Connect wallet" prompt with no additional content.

Capabilities

x402-paymentusdc-basepay-per-callaccount-balancejson-responseno-api-key

Use cases

  • —Querying an account balance via a pay-per-call x402 endpoint
  • —Integrating micropayment-gated data retrieval into agent workflows
  • —Demonstrating x402 protocol usage on the Base network

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need pay-per-call access without API key management
  • —Low-cost per-request data retrieval on Base

Not for

  • —Production use cases requiring documented request/response schemas
  • —High-volume batch queries where per-call pricing is inefficient
  • —Users who need fiat-only payment rails

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/accounts/72/balance
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base), but there is no documentation, no request/response schema, no examples, and the specific endpoint path is not listed among the site's advertised APIs. Docs pages are empty stubs. This is effectively a stub listing.

Warnings

  • —The endpoint /api/v1/accounts/72/balance is not listed among the site's advertised APIs — its purpose is inferred from the URL path only.
  • —No request body schema or response schema is documented anywhere.
  • —All documentation pages (docs, pricing, API, README) resolve to a minimal 'Connect wallet' prompt with no useful content.
  • —The hardcoded account ID '72' in the path suggests this may be a specific resource rather than a general-purpose API.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:51:46Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-28

Agent access

JSONhttps://clawmart.sh/api/listings/zeaGaf
x402-gated account balance endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart