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

# Welcome to Arcade

Choose which Arcade docs you're looking for.

Arcade has two products with their own docs — pick the one you're using.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>🎬</h3></td><td><strong>AI Video</strong></td><td>Generate on-brand teaser videos and product overviews from a prompt.</td><td><a href="https://docs.arcade.software/kb/ai-video/">https://docs.arcade.software/kb/ai-video/</a></td></tr><tr><td><h3>🖱️</h3></td><td><strong>Interactive Demo</strong></td><td>Build clickable product demos with hotspots, steps, and share pages.</td><td><a href="https://docs.arcade.software/kb/interactive-demo/">https://docs.arcade.software/kb/interactive-demo/</a></td></tr></tbody></table>

***

### AI Video

Describe the video you want in a chat with Arcade's AI assistant, and get a polished, on-brand first draft in under a minute — built from your Arcade demos, a brief, or source material you attach. Keep refining it by chatting or editing the timeline directly. Good for teaser videos, sizzle reels, and product overviews with voiceover and your brand kit applied automatically.

### Interactive Demo

Record a walkthrough of your product, then turn it into a clickable demo: add hotspots, callouts, pan & zoom, branching paths, and voiceover, then publish it as a share page or embed it on your site. Good for guided product tours, onboarding flows, and sales demos your audience clicks through at their own pace.


---

# 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.arcade.software/kb/welcome-to-arcade.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.