> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/saga-web-app/working-with-chainlet/configuring-metamask-network.md).

# Configuring Metamask Network

This page includes instructions on how to setup your chainlet network information in your Metamask wallet

The fastest way to configure your chainlet network settings into your metamask browser plugin is by visiting your chainlet's dedicated block explorer page and clicking on the Add \<chainlet name> link present on the footer menus.

You can also see how this looks like in the image included below:

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FWtot6U3ZkYoBt7MZZVsa%2Fexplorer%20mainnet.png?alt=media&amp;token=faad2820-f561-41aa-9710-9022c4520bef" alt=""><figcaption></figcaption></figure>

## Configuring Metamask Network Manually

Navigate to go: Metamask -> Settings -> Networks -> Add Network

The settings screen will look something like this:

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FjmGaLH63iYtAHM6SgsTj%2FScreenshot%202023-04-11%20at%201.51.16%20AM.png?alt=media&amp;token=0f5a824b-2431-4ce4-8acc-aede84fa8ae3" alt=""><figcaption></figcaption></figure>

From here, click on "Add a network manually" and type in the following settings in the required fields:

* **Network Name:** This will be your Chainlet name (in this example I'm using "`abstract`")
* **New RPC URL**: This will be your chainlet's JSON-RPC endpoint, you can get this in [https://app.saga.xyz/](https://app.saga.xyz/launch) -> search your chainlet -> chainlet details -> **RPC Endpoint**
* **Chain ID**: Here you need to input the middle **numerical** part of the ChainID, (make sure to drop the '-1')  Example: `2712762876035000`
* **Currency Symbol**: This is your Chainlet currency symbol. You can get this in in [https://app.saga.xyz/](https://app.saga.xyz/launch) -> search your chainlet -> chainlet details -> on the right of the chainlet name (On the example before `abstract` -> `ABSTR`, ABSTR is the Currency Symbol)               &#x20;
* **Block Explorer URL:** This will be your personal chainlet's block explorer url, you can get this in [https://app.saga.xyz/](https://app.saga.xyz/launch) -> search your chainlet -> chainlet details -> **Block Explorer**

Taken together, the output will look **SIMILAR** with what you see in the following image below:

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FyKk7JK7J5kEvrzOuXKxm%2Fmetamask%20mainnet.png?alt=media&amp;token=228c0ba3-8bfc-4b4f-ab63-9c2c71ce1bd8" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saga.xyz/saga-web-app/working-with-chainlet/configuring-metamask-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.