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

# Features

### 🖱️ No-Code Customization Workflow

A drag-and-drop canvas lets you customize an AI model in minutes. Chain steps for system prompting, RAG or fine-tuning, set parameters and launch with a single click.

> **Why it matters:**
>
> It empowers you to tailor model behavior, or create complex AI models effortlessly, eliminating the need for coding.

### <mark style="color:blue;">📂</mark> Dataset Creation Agent

Upload raw text, PDFs or URLs and the agent automatically cleans, labels and structures the content into a training-ready or retrieval-ready dataset, all inside the browser.

> **Why it matters:**
>
> High-quality data is the hardest part of AI customization. The agent removes that bottleneck so you can focus on outcomes, not data wrangling.

### <mark style="color:blue;">📑</mark> Pre-Built Templates

Choose from ready-made templates for tasks such as customer support bots, knowledge search or domain-specific content generation. Each template ships with recommended prompts, parameters and compute settings.

> **Why it matters:**
>
> You jump straight to a working solution, skipping trial and error and accelerating time to value.


---

# 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.verticalstudio.ai/vertical-products/studio/features.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.