> 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-services.md).

# Vertical Services

Vertical Services is the expansion layer of the Vertical Ecosystem. Through strategic partnerships, advisory, and execution support, we help external teams ship real businesses while connecting their work into a shared network of infrastructure, distribution, and utilities.

> "Extend the ecosystem. Expand the reach."

**Two service arms:**

| Service           | What it does                                                       |
| ----------------- | ------------------------------------------------------------------ |
| Vertical Labs     | Advisory and execution partner for companies looking to enter web3 |
| Vertical Alliance | Network of partner projects connected to the Vertical ecosystem    |

Every project we work with has the opportunity to integrate with VERTAI, expanding the ecosystem's reach and utility.

{% content-ref url="/pages/P2Us5dftvwXtBEYzzUBX" %}
[Vertical Labs](/vertical-services/vertical-labs.md)
{% endcontent-ref %}

{% content-ref url="/pages/HsPuf2ypy7PLkRVtXKFa" %}
[Alliance](/vertical-services/alliance.md)
{% endcontent-ref %}


---

# 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-services.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.