> For the complete documentation index, see [llms.txt](https://docs.rallyprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rallyprotocol.com/unity/embedded-wallets/overview.md).

# Overview

Wallet management is facilitated by the [RallyMobile SDK](/unity/getting-started/overview.md#rallyprotocol), serving as the accounts layer for on-device EOA and on-chain Smart Account operations. It consists of the following features:

### EOA wallets

1. Secure EOA wallet generation & on-device storage, cloud backup & recovery, and the ability to import external EOA wallets. 
2. Developer-friendly APIs for signing both traditional user transactions and [gasless transactions](/unity/gasless-transactions/overview.md) on a mobile device, for use with [RallyTransact](/unity/gasless-transactions/overview.md)

### Smart Account wallets \[coming soon]

1. Dev friendly API to deploy and manage on-chain Smart Accounts wallets, utilizing the EOA generated by the RallyMobile SDK.
2. Developer friendly API to sign [gasless transactions](/unity/gasless-transactions/overview.md) on a mobile device to utilize gasless transactions powered by [RallyTransact](/unity/getting-started/overview.md#rallyprotocol). 


---

# 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://docs.rallyprotocol.com/unity/embedded-wallets/overview.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.