> For the complete documentation index, see [llms.txt](https://liquify-2.gitbook.io/liquify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liquify-2.gitbook.io/liquify/rpc-quickstart-guide/liquify-gateway-dashboard.md).

# Liquify Gateway Dashboard

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

1. You can access your dashboard homepage, manage endpoints, view docs, and contact support by collapsing this sidebar.&#x20;
2. Click the + sign to start adding a new endpoint.
3. View the total number of calls across all your Liquify Gateway endpoints.
4. Analyse the number of successful and failed requests to get a health score across all your RPC endpoints.
5. Analyse weekly and monthly RPC call success rates.&#x20;
6. View all your created endpoints on Liquify Gateway.&#x20;
7. See data for the total number of relays across all your created endpoints.  &#x20;
8. Filter Total Relay data by 24 hours, last 7, 14 and 28 days.&#x20;
9. Connect with Liquify on Discord, Twitter, and by Mail.&#x20;

Take some time to explore and familiarise yourself with the Liquify Gateway portal layout, and [keep an eye out for forthcoming features and upgrades](https://www.liquify.io/blog).


---

# 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://liquify-2.gitbook.io/liquify/rpc-quickstart-guide/liquify-gateway-dashboard.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.