x402basequality 0.35

Check account balance via x402 micropayment on Base network for $0.02 per request.

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

What it does

This endpoint at lowpaymentfee.com returns account balance information for a specific account (account ID 196) behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/196/balance` accepts POST requests and requires an X-PAYMENT header conforming to the x402 protocol (version 1, "exact" scheme). Payment is made in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base) to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The maxAmountRequired is 20000 base units, which equals $0.02 (USDC uses 6 decimals). The endpoint returns JSON.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /api, /pricing, /README) all appear to require a wallet connection and contain no substantive content when crawled without one. As a result, there is very little information about what the response payload looks like or what input parameters (if any) the POST body accepts. The endpoint is confirmed live via a valid 402 challenge.

Capabilities

x402-paymentusdc-baseaccount-balancepay-per-callno-api-key

Use cases

  • —Querying account balance data programmatically with per-call USDC micropayments
  • —Integrating balance lookups into agent workflows without managing API keys
  • —Demonstrating x402 protocol payment flows on Base network

Fit

Best for

  • —Developers experimenting with x402 micropayment protocols
  • —Agents needing keyless, pay-per-call account balance queries
  • —Projects already using USDC on Base that want frictionless API access

Not for

  • —Users needing detailed API documentation or response schemas before integrating
  • —High-volume balance queries where per-call pricing may add up versus subscription models
  • —Users without a Base-network USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI schema, no response examples, and all documentation pages are gated behind wallet connection. The purpose of this specific endpoint (account 196 balance) is vague, and no input/output schema is available beyond the basic outputSchema stub.

Warnings

  • —No documentation accessible without wallet connection — /docs, /api, /pricing, /README all return only 'Connect wallet'
  • —No response schema or example response available; unclear what fields the balance response contains
  • —The endpoint path includes a hardcoded account ID (196); unclear if this is parameterizable or fixed
  • —No OpenAPI specification found

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/GWyDV3
Check account balance via x402 micropayment on Base network for $0.02 per request. — Clawmart · Clawmart