x402-gated account balance endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com provides an account balance lookup via the x402 payment protocol. The specific resource `/api/v1/accounts/88/balance` is gated behind a per-request USDC payment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments of up to 20,000 base units of USDC (0.02 USD per request) settled to a specified wallet address.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no commitments required — payment is handled entirely via the x402 protocol on the Base L2 network.
However, documentation is extremely sparse. The docs, API, pricing, and README 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 the `/accounts/88/balance` endpoint actually returns. The endpoint's purpose — whether it returns a crypto wallet balance, a platform account balance, or something else — is unclear from the available material.
Capabilities
Use cases
- —Querying an account balance via a single paid API call
- —Integrating pay-per-request balance lookups into agent workflows
- —Demonstrating x402 protocol payment flows on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand balance data without API key management
- —Low-volume, pay-as-you-go API consumption
Not for
- —High-volume balance queries where per-call fees add up
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Users who need clear schema definitions before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/88/balance
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to receive data.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. Docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response format
- —Purpose of /api/v1/accounts/88/balance is unclear — no description of what 'account 88' refers to
- —No request or response examples available anywhere in crawled material
Citations
- —Endpoint returns 402 with x402 challenge accepting USDC on Base network at maxAmountRequired 20000 (0.02 USD)https://lowpaymentfee.com/api/v1/accounts/88/balance
- —Platform lists all APIs at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/accounts/88/balance
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs