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

# How It Works

* **Connect Wallet** — Log in by connecting your EVM-compatible wallet.
* **Prompt Submission** — Describe your app in plain English.
* **AI Blueprint Generation** — Our AI generates secure smart contracts, UI, and backend.
* **Deploy Smart Contracts** — You will be prompted to deploy the appropriate smart contract to the HyperEVM Mainnet as described in your prompt.
* **One-Click Deployment** — Build and deploy your app on our infrastructure, making it accessible to everyone.
* **Edit** — Open your app’s directory and customize it to your liking.
* View a complete history of their app’s evolution.
* **Revert** to any previous version with a single click, instantly restoring that build’s smart contracts, UI, and backend.


---

# 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.buildonhype.com/how-it-works.md?ask=<question>&goal=<endgoal>
```

`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.