> For the complete documentation index, see [llms.txt](https://docs.wepin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wepin.io/en/wepin/workspace/add-networks-and-assets.md).

# Networks and Assets Addition

You can configure the network to be used by the wallet integrated with the app. In the *Network* tab, select *Add Network* and search for the network name you wish to use in your app. To view the complete list of supported networks, please refer to the [Supported Blockchains page](/en/wepin/supported-blockchains.md).

<figure><img src="/files/e3L5xNhWhe2JXhMK77ju" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Is the blockchain you need not listed? Please [contact the Wepin](https://wepinwallet.typeform.com/WEPIN-Wallet-EN) team for blockchain support.
{% endhint %}

After adding the network, you need to register the assets that will be displayed to users in the integrated Wepin widget. Depending on the characteristics of your app, you can configure the list of tokens shown to users within the widget. The token list can be deleted or hidden as needed.

<figure><img src="/files/727LJopsaFHUmM9XAyie" alt=""><figcaption></figcaption></figure>

In the case of a multi-chain setup, even if the tokens are the same, they can differ across networks, so you need to add the tokens separately for each network. For example, if you want to add USDT to the token list for both the Ethereum and Polygon networks, you must add USDT for each network separately. Adding USDT on the Ethereum network does not automatically include it on the Polygon network.

<figure><img src="/files/1zo8u95GQg5HqL2r1M5r" alt=""><figcaption></figcaption></figure>


---

# 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://docs.wepin.io/en/wepin/workspace/add-networks-and-assets.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.
