> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/managing-your-wallet/address-book.md). # Address book How to use the Cake Wallet address book to save contacts with addresses for multiple currencies, pick them when sending, and transfer between your own wallets. Cake Wallet includes an address book that lets you save the people and addresses you send to most, so you never have to copy-paste an address twice. Tap the `Contacts` tab in the bottom navigation bar to open it — the screen itself is titled `Address Book`. Contacts can hold addresses for multiple currencies, and the `Wallets` tab lists the addresses of your own wallets for quick transfers between them. When sending, tap the address book icon in the address field to pick a saved contact instead of pasting an address. {% hint style="info" %} For Monero wallets, the `Wallets` tab lists **one address per account** — the first address in each of that wallet's accounts — rather than every subaddress. The `Auto generate subaddresses` setting in `Privacy` settings does not change this. To use a different subaddress, copy it from the `Receive` screen for that account. {% 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.cakewallet.com/features/managing-your-wallet/address-book.md?ask=&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.