> 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/stream.md).

# Stream

Official link: https\://app.verticalstudio.ai/stream

> *"One Chat. Every Model. Any Output."*

<figure><img src="https://3053682209-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGJJb2dKRuk8kJmGBXGp7%2Fuploads%2F7nBVFZJDenKJqNcIfngn%2FScherm%C2%ADafbeelding%202026-01-30%20om%2012.54.45.png?alt=media&amp;token=65cf3510-3141-4933-9486-74682521d96d" alt=""><figcaption></figcaption></figure>

[Vertical Stream](https://app.verticalstudio.ai/stream) is the central hub where users can discover and access 50+ AI models through a single chat interface. Powered by our own model orchestration agent, you can tap into any model for personal or professional projects without managing multiple subscriptions or leaving your chat.

**Who it's for:** Creators, builders, and professionals who want access to all major AI models in one place with one account.

**What it solves:** No more juggling vendors. Copy a prompt, switch models, compare results, and optimize outputs, all in one interface.


---

# 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/stream.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.