> 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/spending-permissions.md).

# Spending permissions

### Budget and per-run caps

Studio reads the published action's limits before setup. Suggested funding amounts fit those limits. A user can choose less; a wider budget is rejected.

### Protected swaps

Single-Cetus protected swaps restrict the adapter, pool, output asset, policy revision, and minimum output. Proceeds settle to the owner and unused input stays in the vault.

The funding preview reads a live quote without submitting a transaction. If the quote is below the published minimum, setup is refused before creation or funding. Prices can change later; the contract checks actual output at execution.

### Other flows

Budget, per-transaction, rate and time rules are enforced on chain. Some protocol, asset and recipient restrictions rely on the compiler and native signer. Legacy bounded flows do not have the same settlement guarantees as the protected swap adapter.

### Expiry and versions

An expired or revoked grant cannot be executed by the Rill signer. Publishing an edited flow creates a new immutable version. Upgradeable Move packages remain separate from action-version approval.<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/spending-permissions.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.