x402basequality 0.30

x402-payable account balance endpoint on Base, settling in USDC at $0.02 per request.

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

What it does

This endpoint at lowpaymentfee.com provides account balance information via the x402 payment protocol. It is part of a broader platform offering multiple API categories — data & analytics, AI/ML inference, finance & Web3, and infrastructure utilities — all priced uniformly at $0.02 per request with no API keys, no rate limits, and no commitments required.

The specific endpoint `/api/v1/accounts/154/balance` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The x402 challenge advertises a maxAmountRequired of 20000 base units, which at 6 decimals for USDC equals $0.02 — consistent with the site's stated pricing. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the "account balance" actually represents or what parameters the POST body expects. The endpoint is confirmed live (402 challenge returned), but the lack of documentation makes it difficult to determine the actual utility or data returned.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-balancejson-responsepay-per-request

Use cases

  • —Querying account balance data with per-request USDC micropayments
  • —Integrating x402-compatible payment flows into agent workflows
  • —Accessing financial data without API key registration

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Low-volume queries where per-request pricing is preferred over subscriptions

Not for

  • —Production workloads requiring well-documented APIs with clear schemas
  • —High-volume use cases where subscription pricing would be more economical
  • —Users who need detailed documentation or support

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what 'account 154 balance' means or what POST body is expected. The listing is effectively a stub.

Warnings

  • —No documentation available — all doc/pricing/API pages render only 'Connect wallet'
  • —No OpenAPI or schema describing request parameters or response format
  • —Purpose of 'accounts/154/balance' is unclear — it may be a demo or placeholder endpoint
  • —No request body schema provided; callers cannot determine required POST parameters

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/gdh3QN
x402-payable account balance endpoint on Base, settling in USDC at $0.02 per request. — Clawmart · Clawmart