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

# Builder

Build the workflow and its spending rules in one place.

### Available actions

Studio compiles Cetus swaps, Haedal stakes, and DeepBook limit orders. Select an action from the library or use a template. Amounts can be supplied at runtime, within the approved limits.

### Budget & permissions

The total budget is the lifetime spending ceiling of the vault. Maximum per run limits one execution. Rate and time limits, asset scopes, and other published restrictions remain part of the action's policy.

Owner funding can narrow published limits. It cannot expand them. A new action version requires fresh approval; existing grants keep their original workflow.

### Preview

Preview builds an unsigned PTB. Anonymous previews do not prove ownership, gas, or funded-vault caps. They are explicitly marked unverified. The local signer must perform a fresh verified simulation before execution.

### Publish

Publish with your owner wallet. Review the action, then choose Approve this action's budget to connect its agent and fund the vault. Publishing itself does not transfer funds.

### Discover contracts

Discover / Import reads a package's public ABI. Imported functions are useful for inspection. Arbitrary ABI functions are not automatically executable, and the compiler refuses unsupported actions.<br>


---

# 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://rillforagents.gitbook.io/rill/builder.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.