> For the complete documentation index, see [llms.txt](https://docs.bolt.observer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bolt.observer/readme/liquidops/getting-started.md).

# Getting started

Let's start by adding a node. To do this, go to your node page and click on the "+ New Node" button as shown in the image below.

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

Once you have identified the node based on its pubkey or alias, click on the "Add node" button. However, if you are adding private nodes (i.e., nodes without announced channels), you'll need to use the pubkey to add them. Here's a snapshot of the process:

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

It's worth noting that the dashboard displayed below only showcases public data collected from the gossip network, such as public channels, total capacity, PubKey, addresses, and so on. To access private data and leverage advanced functionalities, we strongly recommend [setting up LiquidOps.](#user-content-fn-1)[^1] This will allow you to unlock a host of additional features and insights.

<figure><img src="/files/2jMkewN6TlTpaZov6Fly" alt=""><figcaption></figcaption></figure>

Once you've added your first node, you can either continue adding more nodes or start creating workflows.

[^1]:


---

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

```
GET https://docs.bolt.observer/readme/liquidops/getting-started.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.