# Foundry EVM Chain Lookup

> Foundry EVM Chain Lookup 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).

Returns chain metadata (name, native currency, public RPCs, and block explorers) for a given EVM chain ID or name.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/chain-id?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-evm-chain-lookup-dd3e1704
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bPsuSbvI0SHT1qEuMLx75

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-evm-chain-lookup-dd3e1704 -d '<json body>'
```

Example prompt: What are the public RPC endpoints and block explorers for Base (chain ID 8453)?

## When to prefer this

Use this endpoint when an agent needs to programmatically resolve EVM chain metadata — especially RPC URLs or explorer links — from a chain ID or human-readable name, without maintaining a local chain registry. Ideal for multi-chain dApp configuration, wallet setup, or transaction debugging workflows.

## Known failure modes

- Unknown chain ID or name returns an empty chains array
- Malformed or missing input field returns a validation error
- Render.com cold start may cause latency on first request
- Chain data may be stale if chainid.network upstream is not refreshed

## How this service works

EVM chain lookup: chain ID, name, native currency, public RPCs and explorers. Input: a chain ID or name.

## Output

A JSON object containing an array of matching chains, each with: chain name, chain ID, short name, native currency symbol, a list of public RPC URLs, and a list of block explorer URLs. Source attribution (chainid.network) is also included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "A chain ID or name"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chains": [
   {
    "rpc": [
     "https://mainnet.base.org/",
     "https://developer-access-mainnet.base.org/",
     "https://base.gateway.tenderly.co"
    ],
    "name": "Base",
    "chain_id": 8453,
    "explorers": [
     "https://basescan.org",
     "https://base.blockscout.com"
    ],
    "short_name": "base",
    "native_currency": "ETH"
   }
  ],
  "source": "chainid.network"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-evm-chain-lookup-dd3e1704/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)