> 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/getting-started.md).

# Getting started

Rill lets an AI agent run approved Sui actions within a spending budget. You build the action and approve its limits. Your browser wallet keeps ownership of the vault; the agent uses its own local signer.

### Build an action

Open [Builder](https://rill.rifuki.dev/builder). Add a Cetus swap, Haedal stake, or DeepBook limit order. Connect the flow and preview it before publishing.

### Set the budget in Builder

Open Budget & permissions. Set the spending ceiling and any additional restrictions. Publishing saves an immutable action version with those limits.

### Approve funding

After publishing, choose Approve this action's budget. Select your connected agent, choose how much to fund within the published limits, and review the quote. Your wallet approves vault creation, rules and funding, and finally agent access.

### Run the action

Install the Rill plugin in your agent runtime. Ask it to list its Rill actions and run the approved action. The native signer checks the grant and performs a fresh simulation before submission.

### Stop access

Open [Agents](https://rill.rifuki.dev/agent-wallet) and choose Revoke & reclaim. This stops spending from that vault and returns its unused funds. Approved spending limits are not a live remaining-balance display.<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/getting-started.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.