# Foundry Base Token Info

> Foundry Base Token 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 ERC-20 token metadata on Base mainnet (name, symbol, decimals, total supply, contract status) from a given token address.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/base-token-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-token-info-5b780f00
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PD9_jiq5mlgAj1UAFFyXR

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-token-info-5b780f00 -d '<json body>'
```

Example prompt: Can you look up the token info for the Base mainnet contract at 0x532f27101965dd16442E59d40670FaF5eBB142E4 — I need its name, symbol, decimals, and total supply?

## When to prefer this

Choose this endpoint when you need fast, deterministic, on-chain ERC-20 metadata for Base mainnet tokens without any LLM overhead or price oracle complexity. It is the cheapest and most direct way to resolve a token address to its name, symbol, decimals, and supply on Base. Prefer it over generalist blockchain APIs when you specifically need Base mainnet data and want a simple, low-cost per-call model.

## Known failure modes

- Invalid or malformed 0x address returns an error
- Address exists but is an EOA (not a contract) — is_contract will be false, erc20 will be false
- Address is a contract but not ERC-20 compliant — erc20 may be false
- Base mainnet RPC unavailable causing lookup failure
- Network timeout if Render cold-start is triggered

## How this service works

ERC-20 token info on Base mainnet from the chain: name, symbol, decimals, total supply, and whether the address is a contract at all. Input: 0x token address. Deterministic, no LLM, cheapest token lookup.

## Output

Returns a JSON object with: token name, symbol, decimals, total supply (as a float), the address itself, the network identifier (eip155:8453), a boolean indicating whether it is an ERC-20, and a boolean indicating whether the address is a contract at all. If the address is not a contract, relevant fields will reflect that.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "ERC-20 token contract address on Base, 0x + 40 hex characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "Brett",
  "erc20": true,
  "symbol": "BRETT",
  "address": "0x532f27101965dd16442E59d40670FaF5eBB142E4",
  "network": "eip155:8453",
  "decimals": 18,
  "is_contract": true,
  "total_supply": 9999997544.34
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-base-token-info-5b780f00/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)