> For the complete documentation index, see [llms.txt](https://setai-agents.gitbook.io/setai-agents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://setai-agents.gitbook.io/setai-agents/product/images-and-media.md).

# Roadmap

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

Understanding the SETAI Agents progress:&#x20;

#### 🕒 Phase 1 (Oct 2024 - Dec 2024)

AI gather knowledge & human interaction.

Agents Launchpad development, to be integrated with AI agents.

(Finished)

#### 🕕 Phase 2 (Dec 2024 - Feb 2025)&#x20;

Agents Launchpad goes into practice, powered by sentient AI agents.

AI model learn the human qualities, build & train AI to develop its sentient capability.

#### 🕘 Phase 3 (TBA)&#x20;

AI agents go into business, serve & self-refine nonstop, actively following owners' preferences, estimately 02 months from launching: We begin with Agents Launchpad.

*In an ideal world, SETAI Agents will evolve along with society. Think of M3GAN - kinda like that but you can actually turn the power OFF if things go too far.*


---

# 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://setai-agents.gitbook.io/setai-agents/product/images-and-media.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.