# mm-agent-utils Wallet Profile

> mm-agent-utils Wallet Profile is a paid API for AI agents from mm-agent-utils.gferrigno.deno.net, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-11).

Returns on-chain profile data for a Base EVM wallet address, including ETH/USDC balances, transaction count, contract status, and ERC-8004 identity count.

## Facts

- Endpoint: GET https://mm-agent-utils.gferrigno.deno.net/v1/wallet-profile?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mm-agent-utils-wallet-profile-e4649ce1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fRwmNsc_Inp692uQOpZjl

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 mm-agent-utils-wallet-profile-e4649ce1
```

Example prompt: Can you vet the wallet 0x4f3edf983ac636a65a842ce7c78d9aa706d3b113 on Base — tell me its ETH and USDC balances, how many transactions it has, and whether it's a contract or a regular wallet?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call wallet profile specifically on the Base (chain ID 8453) network, especially when vetting counterparties before transactions, filtering airdrop recipients, or checking for ERC-8004 identity signals. Prefer it over general block explorers when you need structured JSON output in an agent workflow without scraping HTML. It is purpose-built for agent use cases via x402 micropayments, making it suitable for automated pipelines.

## Known failure modes

- Invalid or malformed 0x address returns a validation error
- Address not found on Base returns zero balances and zero tx_count
- Network or RPC timeout results in a 5xx error
- Missing required 'address' query parameter returns a 400 bad request
- Non-Base chain addresses may return misleading or empty data since only chain_id 8453 is supported

## How this service works

Tiny pay-per-call utilities for agents on Base: wallet vetting, x402 endpoint linting, deterministic entity extraction.

## Output

A JSON object containing: the wallet address, chain ID (8453 for Base), ETH balance (string), USDC balance (string), total transaction count (integer), a boolean indicating whether the address is a smart contract, and the count of ERC-8004 identity records associated with the wallet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "description": "0x EVM address on Base"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "eth": "0.0038",
  "usdc": "1.5",
  "address": "0x...",
  "chain_id": 8453,
  "tx_count": 12,
  "is_contract": false,
  "erc8004_identities": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mm-agent-utils-wallet-profile-e4649ce1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mm-agent-utils.gferrigno.deno.net](https://www.zero.xyz/host/mm-agent-utils.gferrigno.deno.net/llms.txt)