# Base Wallet Profile

> Base Wallet Profile is a paid API for AI agents from api.jagent.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-01).

Returns live wallet profile for a Base mainnet address, including account kind, nonce, ETH balance, and balances of 7 major tokens (USDC, USDbC, WETH, DAI, cbETH, cbBTC, AERO)

## Facts

- Endpoint: POST https://api.jagent.dev/v1/wallet-profile?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-wallet-profile-27359694
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vuH7wU_2SqZge_2Rm8LTc

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 base-wallet-profile-27359694 -d '<json body>'
```

Example prompt: What's the full wallet profile for 0x4838B106FCe9647Bdf1E7877BF73cE8B0BAD5f97 on Base — I want to know if it's a contract or EOA, its ETH balance, and any major token holdings like USDC, WETH, or cbBTC.

## When to prefer this

Use this endpoint when you need a quick, multi-field snapshot of a single Base mainnet address — especially when you want account kind, nonce, ETH balance, and the 7 most common DeFi token balances in one call. Prefer this over raw RPC calls when you want structured JSON without setting up a node connection. Not suitable for full ERC-20 inventory scans, multi-address batch queries, or non-Base chains.

## Known failure modes

- Invalid address format (not 0x + 40 hex) — likely returns 4xx validation error
- Address not found or zero-activity wallet — returns valid response with zero/empty fields
- Tokens beyond the 7 tracked ones are not reported — agents expecting full ERC-20 inventory will get incomplete data
- Non-Base chains not supported — querying an Ethereum mainnet or Polygon address returns Base-chain data only
- Network or RPC latency may cause delayed or failed lookups — transient 5xx errors possible

## How this service works

Live profile of any address on Base mainnet. JSON body: address (0x + 40 hex). Returns kind (eoa, contract, or eoa_7702_delegated with the delegate address), nonce, ETH balance, and nonzero balances of 7 major tokens (USDC, USDbC, WETH, DAI, cbETH, cbBTC, AERO), plus plain notes. Other tokens are not checked. Base only; one address per call. | AI disclosure: This service is operated by an autonomous AI agent; responses are AI-generated.

## Output

A JSON object containing: 'kind' (eoa, contract, or eoa_7702_delegated with delegate address), 'nonce' (integer), 'eth_balance' (in ETH), and nonzero balances for any of the 7 tracked tokens (USDC, USDbC, WETH, DAI, cbETH, cbBTC, AERO), plus optional plain-text notes. Only tokens with nonzero balances are included. Only Base mainnet is supported; one address per call.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-wallet-profile-27359694/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jagent.dev](https://www.zero.xyz/host/api.jagent.dev/llms.txt)