> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/odk-plugin/wallets.md). # Wallets Documentation regarding wallets Our wallets system allows developers to interact with a player's owned (or delegated) tokens. `BP_ODK_WalletWorldService` and `BPMC_ODK_WalletComponent` are the main classes you may need to interact with. `BPMC_ODK_WalletComponent` provides you with the player's main glyph Wallet Address via `GetPrimaryWallet`. The primary wallet and any optional additional linked wallets are available via `GetLinkedWallets`.\ `BP_ODK_WalletWorldService` provides general token manipulation and inspecting functionality. For any wallet that's associated with a user's account, we automatically listen for all tokens within the wallet, and store those details within the `BP_ODK_WalletWorldService` . Any dynamic changes are also tracked at runtime, and you can bind to the following events to respond to token changes: * `OnTokenAdded` * `OnTokenRemoved` * `OnTokenBalanceUpdated` For more sophisticate token handling, it's recommend that you utilize [Wallet Views](/odk-docs/odk-plugin/wallets/wallet-views.md). --- # 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.otherside.xyz/odk-docs/odk-plugin/wallets.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.