> For the complete documentation index, see [llms.txt](https://docs.zotto.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zotto.ai/introduction.md).

# Introduction

Zotto: An Intent-Driven Smart Agent Hub with a built in Autonomous PerpDEX. Powered by AI. Secured by AA.

## Introduction

At Zotto, we introduce the world's premier automation algorithm, facilitating gasless transactions for perpetual trading, enabling seamless, automated spot trading, and revolutionizing Memecoin Trading. Thereby providing a seamlessly integration of various tasks for an effortless user experience.

Experience the future of trading and DeFi with Zotto – where innovation meets efficiency, and automation reshapes the landscape of traditional financial paradigms.

## Objective

The team behind zotto was established with a singular goal: create an accessible and scalable platform to pioneer a new era of financial autonomy and accessibility, enabling users to navigate the complexities of trading and DeFi with simplicity, security, and unparalleled efficiency.


---

# 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.zotto.ai/introduction.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.