> For the complete documentation index, see [llms.txt](https://docs.desire.acik.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.desire.acik.in/welcome-to-desire-ai.md).
# Welcome to Desire AI
**Desire AI** is a SaaS platform built to automate, standardize, and govern banner creation workflows at scale. It replaces manual, repetitive creative operations with a structured, auditable, and AI-assisted system, enabling teams to move faster without compromising brand control or quality.
For Swiggy, Desire AI enables:
* **Significant reduction in operational effort and manual headcount** involved in banner production
* **Faster turnaround times** for campaign creatives, from brief to publish
* **Strong governance and control** through approvals, audit trails, and version history
* **Seamless scaling of banner production** across cities, languages, formats, and campaign types
At its core, Desire AI bridges creativity and scale—allowing marketing teams to focus on strategy and impact, while the platform reliably handles execution complexity.
### Jump right in
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.desire.acik.in/welcome-to-desire-ai.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.