# Foundry Base Address Info

> Foundry Base Address Info is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-01).

Looks up on-chain facts for a Base network address: wallet vs contract classification, bytecode size, ETH balance, USDC balance, and transaction count.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/base-address-info?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-base-address-info-ae65143b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cxnpOlopHHyyp9YcyJLbW

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 foundry-base-address-info-ae65143b -d '<json body>'
```

Example prompt: Before I send 50 USDC, can you check if 0x11DCED0487cA3E7d9032029DCb302253ccF4e0DE is a wallet or a contract on Base, and tell me its current ETH and USDC balances and how many transactions it's sent?

## When to prefer this

Use this endpoint when you need a quick, deterministic, no-LLM on-chain snapshot of any Base network address before sending funds or interacting with it. It is the right choice when you need to distinguish wallets from contracts, check balances, or assess activity level on Base (eip155:8453) specifically. Prefer alternatives if you need Ethereum mainnet or other chains, or need deeper contract analysis beyond bytecode size.

## Known failure modes

- Invalid or malformed 0x address returns an error
- Address not found or zero activity returns zeros for all balances and transaction count
- Network or RPC node unavailable causes a timeout or 5xx error
- Address input exceeds 42 characters or contains non-hex characters causes validation failure
- Payment failure (x402) if USDC not provided blocks the request

## How this service works

Base address lookup from the chain: wallet (EOA) or contract, bytecode size, ETH balance, USDC balance and number of transactions sent. Useful before sending funds or paying an address. Input: 0x address. Deterministic, no LLM.

## Output

Returns a JSON object with: address kind ('wallet (EOA)' or 'contract'), the queried address, network identifier ('eip155:8453' for Base), code_size (bytes of bytecode, 0 for EOAs), eth_balance (in ETH), usdc_balance (in USDC), and transactions_sent (nonce / outbound tx count).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "Base wallet or contract address, 0x + 40 hex characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "wallet (EOA)",
  "address": "0x11DCED0487cA3E7d9032029DCb302253ccF4e0DE",
  "network": "eip155:8453",
  "code_size": 0,
  "eth_balance": 0,
  "usdc_balance": 0.053,
  "transactions_sent": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-base-address-info-ae65143b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)