# nani/acc (⌘, ⌘)

<figure><img src="/files/PpJxp58ZJK70OTMfbJoj" alt="" width="188"><figcaption></figcaption></figure>

This means you or your users can have sponsored transactions ([*no gas to use dapps*](https://www.erc4337.io/)), use other tokens and even yield (*see* [*NEETH*](/nani/nani-acc/neeth.md)) in place of gas, as well as enjoy more automations around security than your typical wallet or EOA.

### **agency onchain**

nani accounts are also [*fully agentic* (nani/acc)](https://hackmd.io/-I8NmV0eSraztwi_gQOFpQ).  They natively support text and more human interactions and delegation.

This means that they are designed to[ follow commands (⌘)](https://github.com/NaniDAO/ie) and [action plans](https://github.com/NaniDAO/accounts/tree/main/src/validators) such as DCA or opportunistic swapping ("sniping").&#x20;

Unlike other bot wallets, [nani accounts](https://github.com/NaniDAO/accounts) are fully self-custodial and can install safeguards using a [minimal modular standard](https://ercs.ethereum.org/ERCS/erc-7582) for plugin apps. This is the benefit and unlock of turning wallets into code and nani/acc.

Let's get started with the following primers which help complete the picture for *smarter accounts*:

* [*App*](/nani/nani-acc/app.md)
* [*Account*](/nani/nani-acc/account.md)
* [*Accounts Factory*](/nani/nani-acc/accounts.md)
* [*NEETH (Self-Repaying)*](/nani/nani-acc/neeth.md)
* [*IE (Texting Transactions)*](/nani/nani-acc/ie.md)
* [*NANI DAO (Governance)*](/nani/nani-acc/dao.md)


---

# Agent Instructions: 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:

```
GET https://nani.gitbook.io/nani/nani-acc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.