> 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/getting-started/network.md).

# Network

## Overview

Pharos provides two primary network environments to help you move from development to production smoothly.

Whether you're experimenting with smart contracts or deploying a live application, each network is designed to support a specific stage of your workflow.

## Available Networks

* **Atlantic Testnet**\
  This is where you build and test. Use it to deploy contracts, try out integrations, and iterate on your application without worrying about real assets.
* **Pacific Mainnet**\
  This is the production network. Once your application is ready, you can deploy to Mainnet and interact with real users, assets, and infrastructure.

## Which One Should You Use?

In most cases:

* Start on **Atlantic Testnet** while developing and testing
* Move to **Pacific Mainnet** when you're ready to go live


---

# 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.pharos.xyz/getting-started/network.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.