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

What it does

This endpoint at lowpaymentfee.com provides an account balance lookup via the x402 payment protocol. The specific resource `/api/v1/accounts/133/balance` is gated behind a per-request USDC payment on the Base network. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD per request), consistent with the provider's advertised flat $0.02/request pricing across all their API endpoints.

The provider, lowpaymentfee.com, hosts a broader suite of x402-gated APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share the same $0.02/request pricing model with no API keys, no rate limits, and no minimum commitments — payment is handled entirely via the x402 protocol using USDC on Base.

This particular endpoint appears to return account balance information in JSON format. However, documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what parameters the endpoint accepts or what fields the response contains. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes integration speculative.

Capabilities

x402-paymentusdc-on-baseaccount-balancepay-per-requestno-api-key

Use cases

  • —Querying account balance information via a single paid API call
  • —Integrating pay-per-request balance lookups into agent workflows
  • —Demonstrating x402 protocol usage for micropayment-gated endpoints

Fit

Best for

  • —Developers experimenting with x402 payment protocol integration
  • —Agents needing on-demand account balance data without API key management
  • —Low-volume, pay-as-you-go balance queries

Not for

  • —High-volume balance monitoring requiring bulk or subscription pricing
  • —Use cases requiring detailed API documentation and guaranteed SLAs
  • —Production systems needing well-documented request/response schemas

Quick start

# The endpoint requires an x402 payment header (USDC on Base).
# 1. POST to the endpoint without payment to receive the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/accounts/133/balance
# 2. Use an x402-compatible client to fulfill the payment challenge
#    and re-submit with the X-PAYMENT header.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge and consistent pricing. However, there is no OpenAPI schema, no request/response examples, and all documentation pages render only a wallet-connect prompt. The purpose of this specific endpoint (account 133 balance) is unclear and undocumented, making this effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, and API pages all show only 'Connect wallet'
  • —No OpenAPI or request/response schema provided
  • —The specific endpoint path references a hardcoded account ID (133); unclear if this is parameterizable
  • —Purpose and response format of the balance endpoint are entirely undocumented

Citations

Provenance

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

Agent access

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