# Actions, Networks, and Tokens supported

## Chains supported

**EVMs**:

* Ethereum 
* Base
* Optimism
* Arbitrum
* ZK Sync
* Polygon
* Blast
* Scroll
* Gnosis chain
* Taiko
* Binance Smart Chain
* Avalanche
* Mode
* Linea

Currently on the Brian App, only the EVM chains are supported.

**Non EVMs**:

* Starknet
* Solana

## Actions supported

Brian API supports the following actions:

* transfer
* swap
* bridge and cross-chain swap\*
* deposit°
* withdraw°
* borrow and repay (AAVE)
* ENS actions (registration, renewal, resolution, etc..)\*\*
* balance

***

\*the **bridge** action is currently not supported from/to Solana and Starknet

°the **deposit** and **withdraw** (from/to DeFi protocol) actions are only supported on:

* Ethereum mainnet
* Arbitrum
* Optimism
* Polygon
* Base
* Avalanche

Check [this page](/brian-api/apis/transaction/actions-networks-and-tokens-supported/deposit-and-withdraw-to-from-defi-protocols.md) to learn more.

\*\*the ENS-related actions are only supported on Ethereum mainnet, while any ENS subdomain (even L2 subdomains) resolution is supported both in the prompt and in the `address` body parameter.

***

## Solvers

For the swap, bridge, and cross-chain swap operations, Brian leverages the following solvers:

* [Enso](https://www.enso.finance/) 
* [Bungee](https://docs.bungee.exchange/)
* [LiFi](https://li.fi/)
* [Portals](https://build.portals.fi/)
* [Symbiosis](https://symbiosis.finance/)
* [Avnu.fi](https://www.avnu.fi/)
* [Jupiter](https://jup.ag/)

Offering best routes for swap, cross-swap, and bridge operations on different chains. 

***

## Tokens

The Brian-supported token list consists of internal token lists and external provider lists, such as:

* EVM tokens

{% embed url="<https://apidocs.li.fi/reference/get_v1-tokens>" %}

* Starknet tokens:

{% embed url="<https://doc.avnu.fi/avnu-spot/token-list/token-list-api>" %}

* Solana tokens:

{% embed url="<https://station.jup.ag/api-v6/get-tokens>" %}


---

# Agent Instructions: 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:

```
GET https://docs.brianknows.org/brian-api/apis/transaction/actions-networks-and-tokens-supported.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.