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

What it does

This endpoint at lowpaymentfee.com provides a pay-per-request API for retrieving account balance information. It is part of a broader platform that offers dozens of x402-gated endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/200/balance` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The maximum amount required is 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely sparse — the docs, API, pricing, 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 explanation of what the balance endpoint actually returns or what parameters it accepts. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know exactly what data is returned or how to structure a request body.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-balancepay-per-requestno-api-keyjson-response

Use cases

  • —Querying account balance data with per-request USDC micropayments
  • —Integrating pay-as-you-go balance lookups into agent workflows
  • —Accessing financial data without API key registration

Fit

Best for

  • —Agents or services that need on-demand account balance data without subscription commitments
  • —Developers experimenting with x402 payment protocol integrations
  • —Use cases requiring keyless, permissionless API access on Base

Not for

  • —Production systems requiring well-documented, schema-validated APIs
  • —High-volume use cases where per-request pricing may add up versus bulk plans
  • —Users who need detailed documentation or support before integrating

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, confirming it works. 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 balance for account ID 200) is unclear and undocumented.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —All documentation pages (docs, API, pricing, README) are empty — only show 'Connect wallet'
  • —No request body schema or response schema provided — unclear what parameters are accepted or what data is returned
  • —The endpoint path includes a hardcoded account ID (200); it is unclear if this is parameterizable or what accounts are available
  • —The broader platform lists many endpoints but none appear to have detailed documentation

Citations

Provenance

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

Agent access

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