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

# Account Overview

The Mono Protocol Toolkit is compatible with embedded signer providers such as Turnkey and Privy, as well as with applications that have direct access to signer keys (such as Web3 wallets and centralized exchanges).

The Toolkit utilizes accounts that are compatible with gas abstraction on all chains, so users never have to worry about paying gas. Key account features include:

**Universal Smart Wallets:**

* **Programmable Logic**: Custom validation rules across all chains
* **Session Management**: Temporary permissions for specific applications
* **Spending Controls**: Built-in limits and approval workflows across networks
* **Social Recovery**: Multi-chain account recovery mechanisms

**Cross-Chain Identity:**

* **Unified Addres**s: Same address across all supported chains
* **Permission Sync**: Consistent access controls and preferences
* **Metadata Management**: Cross-chain user data and preferences
* **Privacy Controls**: Selective disclosure across different networks


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://monoprotocol.gitbook.io/monoprotocol/architecture/account-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
