Check account balance via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns account balance information for a specific account (account ID 102) behind an x402 paywall. It is part of a broader platform offering numerous pay-per-call APIs 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/102/balance` accepts POST requests and is gated by the x402 protocol (version 1, "exact" scheme). The payment challenge requires up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.
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 fields the balance response contains or what request body (if any) is expected. The endpoint is confirmed live (returns 402 with a valid x402 challenge), but the actual functionality and response format remain unknown.
Capabilities
Use cases
- —Querying account balance data with per-request USDC micropayments
- —Integrating balance checks into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents needing keyless, pay-per-call account balance lookups
- —Projects already operating on the Base L2 network with USDC
Not for
- —Production use cases requiring documented request/response schemas
- —High-volume balance queries where per-call pricing is inefficient
- —Users who need fiat payment rails or non-crypto settlement
Quick start
# 1. Send a POST to the endpoint — you'll get a 402 with payment details
curl -X POST https://lowpaymentfee.com/api/v1/accounts/102/balance
# 2. Parse the 402 JSON challenge, construct an x402 payment header
# using USDC on Base (max 20000 base units = $0.02), then retry:
curl -X POST https://lowpaymentfee.com/api/v1/accounts/102/balance \
-H "X-PAYMENT: <signed-x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge, but there is zero documentation on request body format, response schema, or what 'account balance' actually returns. Docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are completely unknown
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no technical content
- —The specific purpose of 'account 102 balance' is unclear — it may be a demo or placeholder endpoint
- —No examples of successful responses exist in the crawl material
Citations
- —Endpoint returns 402 with x402 v1 challenge requiring up to 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/102/balance
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/102/balance
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs