# DataBG Wallet Balance Lookup

> DataBG Wallet Balance Lookup is a paid API for AI agents from api.databg.tech, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns the current ETH and Wei balance of a given blockchain wallet address, including network metadata.

## Facts

- Endpoint: POST https://api.databg.tech/v1/tools/wallet/balance
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/databg-wallet-balance-lookup-bf20d772
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5ru7OdC_14Y0PlumvVcgZ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability databg-wallet-balance-lookup-bf20d772 -d '<json body>'
```

Example prompt: What's the current ETH balance of wallet address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e? Give me the balance in both ETH and Wei along with the network details.

## When to prefer this

Choose this endpoint when you need a fast, pay-per-call blockchain wallet balance lookup without managing your own RPC node or Web3 infrastructure. Ideal for AI agents that need on-demand balance checks as part of automated workflows, especially when using x402 micropayment rails for frictionless billing.

## Known failure modes

- Invalid or malformed wallet address returns an error or success:false
- Network unavailable or RPC node down causes a timeout or failure response
- Non-Ethereum address formats may not be supported
- Address with no on-chain history may return zero balance with success:true

## How this service works

Global structured data and machine-payable tools built for AI agents, developers and intelligent applications.

## Output

Returns a JSON object containing the wallet balance in both ETH (human-readable string) and Wei (raw integer string), along with the network name, chain ID, network ID, RPC endpoint used, the asset type, the queried address, a success boolean, and an ISO 8601 timestamp of when the query was made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "address": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rpc": {
   "type": "string"
  },
  "asset": {
   "type": "string"
  },
  "address": {
   "type": "string"
  },
  "network": {
   "type": "string"
  },
  "success": {
   "type": "boolean"
  },
  "chain_id": {
   "type": "integer"
  },
  "network_id": {
   "type": "string"
  },
  "queried_at": {
   "type": "string",
   "format": "date-time"
  },
  "balance_eth": {
   "type": "string"
  },
  "balance_wei": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/databg-wallet-balance-lookup-bf20d772/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.databg.tech](https://www.zero.xyz/host/api.databg.tech/llms.txt)