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

# What is Skynet?

Skynet is a modular, no-code platform that enables anyone to create intelligent, commerce-ready agents for the Virtuals Protocol ecosystem. Our platform combines:

* **🎨 Visual Builder** - Drag-and-drop interface
* **🤖 AI Integration** - Multiple LLM providers
* **⛓️ Web3 Native** - 250+ blockchain integrations
* **💰 ACP Ready** - Instant commerce capabilities
* **🔌 8,000+ Tools** - MCP protocol integration

```
User Ideas → Visual Builder → Agent Logic → ACP Integration → Live Agent
     ↓              ↓             ↓            ↓            ↓
  Business      Drag & Drop    AI + Web3    Commerce     Revenue
   Vision       Interface      Components    Ready       Generation
```

**Key Benefits**

* **10,800% Faster** - 5 minutes vs 6 months
* **Zero Code Required** - Visual workflow building
* **Commerce Ready** - Built-in ACP integration
* **Ecosystem Native** - Virtuals Protocol optimized
* **Unlimited Scalability** - Enterprise-grade infrastructure


---

# 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://docs.skynetxbt.ai/documentation/getting-started/editor.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.