Wallet Balance API.
Check the native ETH balance of an EVM wallet on Base Mainnet and return precise machine-readable blockchain data.
Blockchain balance
as structured data.
Query a Base Mainnet wallet and receive the native ETH balance without running your own RPC integration.
GET /v1/tools/wallet/balance
Pass a valid EVM address using the address query parameter.
Base Mainnet
The tool returns both exact balance in wei and a human-readable ETH representation.
Agentic blockchain workflows
Useful for wallet screening, automation, portfolio workflows and blockchain-aware AI agents.
Built for autonomous calls.
Discover the API schema and x402 payment requirements from the DataBG machine-readable API.
View OpenAPI →API reference for AI agents and developers.
DataBG tools are designed as small, machine-readable building blocks for automated workflows. Each request uses a predictable HTTP endpoint and can be accessed with an API key or, where enabled, through x402 machine payments.
Read a Base Mainnet wallet balance as structured data
The DataBG Wallet Balance API lets AI agents and applications query the native ETH balance of an EVM wallet on Base Mainnet without implementing their own RPC integration.
Request
GET https://api.databg.tech/v1/tools/wallet/balance?address=0x...Required parameter: address — a valid EVM wallet address.
Returned balance information
The tool is designed to return both the exact native balance in wei and a human-readable ETH representation. Keeping the integer wei value available is useful for software that needs precise arithmetic without floating-point conversion.
Use cases for AI agents
Wallet balance data can be used in blockchain-aware agents, portfolio workflows, wallet screening, payment checks, automation and applications that need to make decisions based on an EVM address.
Network
The current tool targets Base Mainnet. It reports the native ETH balance on that network; it is not a generic multi-chain token portfolio endpoint.
Access and pricing
The listed price is $0.002 per request in USDC on Base Mainnet. Clients can use an authorized DataBG API key or the supported x402 payment flow.
How x402 access works
DataBG paid tools can use the HTTP 402 Payment Required flow. A compatible client requests a resource, receives machine-readable payment requirements, settles the requested amount in USDC on Base Mainnet, and retries the request with payment authorization. This model is designed for autonomous software that can discover and pay for individual API calls.
Agent → DataBG endpoint
↓
402 Payment Required
↓
USDC payment on Base Mainnet
↓
Retry with payment authorization
↓
Structured JSONFor implementation details, use the live API specification and machine-readable discovery resources linked below.
Open API specification → Machine-readable discovery →