> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/build-on-coti/core-concepts/onboard-user.md). # Account Onboarding Procedure Account Onboarding is a procedure that is needed to acquire the EOA unique AES key, which is needed when the wallet wishes to perform GC related on-chain computation operations; that is when the AES key is being used (e.g. encryption and decryption). Once the EOA is created and funded with native coin, it needs to be onboarded to the system to obtain an AES key. For a plain-language explanation for end users, see [What Is Onboarding?](/coti-documentation/build-on-coti/core-concepts/what-is-onboarding.md). See the [guide for onboarding an account](/coti-documentation/build-on-coti/guides/account-onboard.md). After completing the Account Onboard step the wallet has a functional account with the necessary credentials (having own AES key) allowing it to start interacting with the gcEVM operations, including running smart contracts or performing other actions as needed. You can fund accounts using the [COTI Faucet](/coti-documentation/networks/testnet/faucet.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 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://docs.coti.io/coti-documentation/build-on-coti/core-concepts/onboard-user.md?ask=&goal= ``` `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.