# ChainScope Wallet Balance

> ChainScope Wallet Balance is a paid API for AI agents from chainsscope.duckdns.org, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Retrieves the native token balance for a wallet address on Ethereum, Base, Bitcoin, or Solana via a single unified interface

## Facts

- Endpoint: POST https://chainsscope.duckdns.org/tools/wallet-balance
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainscope-wallet-balance-8faf4978
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__tUsRHgjmJ3V2JpN3uFOP

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 chainscope-wallet-balance-8faf4978 -d '<json body>'
```

Example prompt: What's the native ETH balance of wallet address 0x1f5f8474fA0dc1Fde79187abd68Ef8Ea15ADAe34 on Ethereum?

## When to prefer this

Choose this endpoint when you need a simple, unified native balance lookup across Ethereum, Base, Bitcoin, or Solana without maintaining four separate chain integrations. It is ideal for agents that need quick balance checks on multiple chains through one consistent interface and one payment model, rather than wiring up and maintaining individual chain RPC connections.

## Known failure modes

- Invalid or malformed wallet address returns an error or empty result
- Unsupported chain identifier causes a bad request error
- Network timeout if the underlying RPC node is unresponsive
- Address with zero balance may return '0' balance rather than an error
- DuckDNS dynamic hostname may have availability or DNS resolution issues

## How this service works

Native balance for a wallet address, with one consistent response shape across Ethereum, Base, Bitcoin, and Solana -- no need to integrate each chain's RPC/explorer separately yourself.

## Output

Returns a JSON object containing the queried chain name, the wallet address, the native token symbol (e.g. ETH, BTC, SOL), and the native token balance as a string representing the amount held at that address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "bitcoin",
    "solana",
    "arbitrum",
    "optimism",
    "polygon"
   ],
   "type": "string"
  },
  "address": {
   "type": "string",
   "description": "wallet address for the given chain"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "ethereum",
  "address": "0x1f5f8474fA0dc1Fde79187abd68Ef8Ea15ADAe34",
  "native_symbol": "ETH",
  "native_balance": "1.5"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainscope-wallet-balance-8faf4978/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainsscope.duckdns.org](https://www.zero.xyz/host/chainsscope.duckdns.org/llms.txt)