> For the complete documentation index, see [llms.txt](https://rocket-3-1.gitbook.io/rocket-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rocket-3-1.gitbook.io/rocket-3/abstract.md).

# Abstract

**Rocket-3 is a platform that helps users conveniently complete on-chain transactions while minimizing gas fee costs as much as possible and prioritizing order sorting.**&#x20;

Rocket-3 will achieve this through a hybrid solution, maximally solving the problem of cumbersome trading workflows for users. We integrate the required steps traditionally involved in trading into one platform, reducing time friction for users to make trading decisions, while using “Boost up” to lower transaction costs as much as possible.&#x20;

Rocket-3 also develops AI tools, using Large Language Models in the background to aid trading path decisions and provide event tracking analysis. This solves the problem of time friction.


---

# 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://rocket-3-1.gitbook.io/rocket-3/abstract.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.
