> 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/using-the-agent-plugin.md).

# Using the agent plugin

### Install Rill

Install the Rill plugin from the rifuki/rill marketplace in your supported agent client. The launcher downloads the native signer and verifies a pinned checksum before starting MCP.

The hosted API constructs unsigned transactions and holds no wallet keys. Signing runs locally in the agent runtime.

### Check readiness

Run the installed signer to inspect its public address, network, and readiness:

\`\`\`sh\
\~/.rill/bin/rill-wallet status\
\`\`\`

A valid owner-signed grant allows rill\_run\_action without a global run-set. Generic rill\_execute requires a run-set. Mainnet signing also requires explicit local configuration.

### Execute

Ask the agent to list its Rill actions, choose the intended action and vault, then run it. Budget exhaustion, revocation, altered grants, and a minimum-output failure result in refusal. Do not automatically lower the owner's floor or bypass a refusal.<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/using-the-agent-plugin.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.