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/195/balance

What it does

This endpoint at lowpaymentfee.com provides an account balance lookup (account ID 195) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all gated via the x402 protocol on the Base network.

The specific endpoint `/api/v1/accounts/195/balance` accepts POST requests and returns JSON. Payment is settled in USDC on Base (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The platform advertises a flat $0.02 per request across all its endpoints, with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the balance endpoint actually returns. The endpoint is confirmed live via a valid 402 challenge, but the lack of documentation makes it difficult to know what data to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-balancepay-per-calljson-api

Use cases

  • —Querying account balance information for account 195 via a single paid API call
  • —Demonstrating x402 protocol integration for pay-per-request APIs
  • —Agent-driven balance lookups without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Quick one-off account balance queries

Not for

  • —Production use requiring documented request/response schemas
  • —High-volume balance monitoring (no documented rate limits but no SLA either)
  • —Users without USDC on Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The purpose of this specific endpoint (account 195 balance) is unclear, and there is no way to know what the response looks like without paying.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README pages are all empty stubs
  • —No OpenAPI or request/response schema provided
  • —Purpose of 'account 195 balance' is unclear — may be a demo or placeholder
  • —No SLA, rate limit, or uptime guarantees documented

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 01:46:32Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-30

Agent access

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