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

# Introduction

## What is Rosvelt?

**From docs to deploy. Ship software faster.**

Rosvelt is the all-in-one platform where AI agents write the docs, build the product, run the tests, and release it — end to end. You just review and ship.

### **Key value propositions**

* **Ships in hours, not weeks** — \~15x faster than traditional development. Your agents work around the clock.
* **Production-grade code** — Clean, maintainable, enterprise-ready code. Not messy AI autocomplete.
* **Works with your stack** — Slack, GitHub, Figma, Vercel, and more. Native integrations with the tools you already use.
* **Autonomous agents that actually ship** — Configure once, deploy everywhere. Your agents understand full codebase context, collaborate on tasks, and self-correct without intervention.

You can login trought and start our guide <https://rosvelt.com/auth>

<figure><img src="https://1271168736-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6wuI4Odwz9aO3o0uh5xn%2Fuploads%2FBof3Lb9TORg4Q3KJzfZb%2Fimage.png?alt=media&amp;token=00e77291-f176-4190-b85f-29974c9f111a" alt=""><figcaption></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://rosvelt.gitbook.io/docs/introduction/introduction.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 `build a script that syncs our docs to a CMS` 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.