x402basequality 0.30

x402-gated account balance endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes an account balance lookup at `/api/v1/accounts/21/balance` behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider, lowpaymentfee.com, hosts a broader catalog of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services (geocoding, validation, conversion, generation), all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/accounts/21/balance` endpoint. The exact response schema and the meaning of "account 21" are not documented in the crawled material.

The endpoint is confirmed live: the probe received a proper HTTP 402 challenge with x402 version 1 headers. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so details about request parameters, response fields, and error handling are unknown.

Capabilities

x402-paymentusdc-baseaccount-balanceper-call-pricingno-api-keyjson-response

Use cases

  • Querying account balance data via a single paid API call
  • Agent-driven balance lookups without pre-registration or API keys
  • Programmatic access to account information settled in USDC on Base

Fit

Best for

  • AI agents that need keyless, pay-per-call API access
  • Developers experimenting with x402 payment protocol integrations
  • Scenarios requiring low-friction, no-subscription data access

Not for

  • High-volume balance polling where $0.02/request adds up quickly
  • Users who need detailed documentation or guaranteed SLAs before integrating

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and no explanation of what 'accounts/21/balance' actually returns. All doc pages render only a wallet-connect prompt. The listing is essentially a stub.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README all return only a 'Connect wallet' prompt with no content.
  • The meaning of 'accounts/21/balance' is unexplained; it is unclear what account 21 refers to or what the response contains.
  • No request body schema or response schema is provided anywhere in the crawled material.
  • The broader site advertises many endpoints but none have documented behavior beyond a title and price.

Citations

Provenance

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

Agent access

x402-gated account balance endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart