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 153) behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call APIs 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/153/balance` accepts POST requests and requires an X-PAYMENT header conforming to the x402 protocol (version 1, scheme "exact"). Payment is made in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base) to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. The response MIME type is application/json.
Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no example request/response payloads, and no description of what fields the balance response contains. The endpoint is confirmed live (returns 402 challenge correctly), but the lack of documentation makes it difficult to know what data is actually returned or what input parameters (if any) the POST body should contain.
Capabilities
Use cases
- —Querying account balance data with per-call USDC micropayments
- —Integrating pay-per-use balance lookups into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Projects requiring low-friction micropayment-gated endpoints
Not for
- —Production use cases requiring documented response schemas and SLAs
- —High-volume balance queries where per-call pricing is inefficient
- —Users without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/153/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but documentation is essentially nonexistent — docs/pricing/README pages all show only 'Connect wallet'. No OpenAPI spec, no example payloads, no description of response fields. The purpose of this specific endpoint (account 153 balance) is unclear beyond the URL path.
Warnings
- —No documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or schema describing request body or response fields
- —Purpose of 'account 153 balance' is unexplained — may be a demo or placeholder
- —No example responses available to verify what data is returned
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/accounts/153/balance
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/accounts/153/balance
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/accounts/153/balance
- —Docs, pricing, API, and README pages render only 'Connect wallet'https://lowpaymentfee.com/docs