> For the complete documentation index, see [llms.txt](https://archer-bot.gitbook.io/archer.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archer-bot.gitbook.io/archer.bot/reference/supported-tokens-and-networks.md).

# Supported Tokens & Networks

Archer is multi-chain by default. Eight networks are live today across EVM and Solana, with full swap, bridge, and send support on every one.

## Supported Chains

| Chain     | Native Token | Chain ID | Swaps | Bridges | Sends |
| --------- | ------------ | :------: | :---: | :-----: | :---: |
| Ethereum  | ETH          |     1    |   ✅   |    ✅    |   ✅   |
| Arbitrum  | ETH          |   42161  |   ✅   |    ✅    |   ✅   |
| Base      | ETH          |   8453   |   ✅   |    ✅    |   ✅   |
| Polygon   | POL          |    137   |   ✅   |    ✅    |   ✅   |
| Optimism  | ETH          |    10    |   ✅   |    ✅    |   ✅   |
| Avalanche | AVAX         |   43114  |   ✅   |    ✅    |   ✅   |
| BSC       | BNB          |    56    |   ✅   |    ✅    |   ✅   |
| Solana    | SOL          |     —    |   ✅   |    ✅    |   ✅   |

## Tokens

Archer supports thousands of tokens — every ERC-20 indexed by Bungee/1inch on EVM chains, and every SPL token indexed by Jupiter on Solana. The token database is continuously synced.

### Major Tokens (Always Available)

* **Stablecoins**: USDC, USDT, DAI, USDS
* **Native L1/L2 gas tokens**: ETH, SOL, POL, AVAX, BNB
* **L2 governance**: ARB, OP
* **Major memecoins**: PEPE, SHIB, BONK, WIF
* **Wrapped/staking derivatives**: WETH, WBTC, stETH, mSOL

### Resolving Tokens

Archer resolves tokens by ticker or contract address. When a ticker is ambiguous (e.g., "USDC" exists on every chain), Archer disambiguates from your prompt or balances. See [Token Lookups](/archer.bot/intents/token-lookups.md) for details.

### Spam Filtering

Tokens flagged in Archer's spam database are filtered from balances and blocked from swaps, bridges, and sends. See [Token Safety & Spam Detection](/archer.bot/intents/token-safety-and-spam-detection.md).

## Aggregators and Routing

| Operation           | Provider                       |
| ------------------- | ------------------------------ |
| EVM swaps           | Bungee (multi-DEX aggregation) |
| Solana swaps        | Jupiter                        |
| Cross-chain bridges | DeBridge DLN (via Bungee)      |
| EVM token prices    | Moralis, CoinGecko             |
| Solana token prices | Jupiter, CoinGecko             |
| EVM balances        | Moralis                        |
| Solana balances     | Helius RPC                     |

Archer always picks the best route across the available aggregators — you don't pick a venue, you pick an outcome.

## What's Coming

* Additional EVM L2s (Linea, Scroll, zkSync, Mantle) — pipeline is ready, gating on usage demand
* Native Bitcoin support (via wrapped representations and bridge integrations)
* Cosmos / IBC chains (longer-term)

For requests on specific chains or tokens, reach out at [archerprotocol.com/contact](https://archerprotocol.com/contact).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://archer-bot.gitbook.io/archer.bot/reference/supported-tokens-and-networks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.