> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/tooling-and-infrastructure/rpc/zan.md).

# ZAN RPC

ZAN Node offers stable and fast RPC connections to Pharos Network, while providing a range of enhanced capabilities to data retrieval API and dynamic monitoring of smart contracts and assets.

## How to Access Pharos Testnet RPC from ZAN?

### Step 1: Create a ZAN account

A ZAN account is required if you want to create an API key on the ZAN platform for configuring an RPC node service on Pharos. For more information, see [Preparing a ZAN account](https://docs.zan.top/docs/quick-start-guide#-preparing-a-zan-account).

### Step 2: Create the API key required for configuring RPC Service on Pharos Network

If you want to configure the RPC node service network, you need to create an API key on the ZAN platform. This key is used for verification during node connection. You [can create the API key on the ZAN platform](https://docs.zan.top/docs/quick-start-guide#-creating-your-api-key-on-the-zan-platform). After the API key is created, you can get the URLs for the Pharos Network.

### Step 3: Copy your network URL

After the API key is created, you can get the URLs that can be used for accessing Pharos Network. Search for Pharos in the Chain RPC section. Click Copy to the right of the HTTPS URL to quickly copy the URL.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeS_l7R2_PVVOMygh4Hy0Z8jNmeG1ZIsubVgkttcuOgfSbSTCrrFG60fX2SlbWSjI5EPGPGzlsE0HYoZ1trmuhtprjUkM6rvU_xNQfhYAQzH8sB42NWgE6T2OpP-8uwTT-57dWRzw?key=gOwVsY2HEJ_jkvNt_voFYQ" alt=""><figcaption></figcaption></figure>

### For Example:

| Network          | HTTPS URL                                                | WSS URL                                                 |
| ---------------- | -------------------------------------------------------- | ------------------------------------------------------- |
| Atlantic Testnet | <https://api.zan.top/node/v1/pharos/testnet/{apikey}>    | wss\://api.zan.top/node/ws/v1/pharos/testnet/{apikey}   |
| Pacific Mainnet  | <https://api.zan.top/node/v1/pharos/mainnet/{api\\_key}> | wss\://api.zan.top/node/ws/v1/pharos/mainnet/{api\_key} |

### Video Reference: [Pharos RPC.mp4](https://drive.google.com/file/d/1fMDF24yQu3xtnqQCOyQc9141Regfe1Ak/view?usp=sharing)


---

# 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.pharos.xyz/tooling-and-infrastructure/rpc/zan.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.