> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/credential-wallet/truvera-mobile-wallet.md).

# Truvera Mobile Wallet

The Truvera Mobile Wallet is a full-featured identity wallet that is freely available in major app stores to help consumers take control of their identity data.

Though the Truvera Wallet could be used in production, most solutions will benefit from a custom wallet experience using one of the solutions [described in the wallet overview](https://docs.truvera.io/credential-wallet.md). The Truvera Wallet is most often used as a development tool by

* Educating stakeholders on the capabilities of an identity wallet,
* Evaluting a proof-of-concept approach,
* Eliminating veriability when testing issuance and verification.

## Download the wallet

To see the full capabilities of the Truvera mobile wallet, you can download it from an app store:

* iOS users: Download from the the [App store](https://apps.apple.com/br/app/truvera-wallet/id6739359697)
* Android users: Download from the [Google Play store](https://play.google.com/store/apps/details?id=com.truvera.app)

{% hint style="info" %}
Truvera Wallet supports devices that have Android 8.1 or higher and iOS 11 or higher.
{% endhint %}


---

# 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.truvera.io/credential-wallet/truvera-mobile-wallet.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.
