> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/user-guide/getting-started/opening-an-account.md). # Opening an Account ## Individuals To open an account, visit [app.architect.co](https://app.architect.co/) and select the "Get Started" button. Follow the prompts to create an account and login.

Once you've logged in, you will be guided through the KYC and account verification process. If you need to resume progress on an application, visit or click the settings icon in the upper right to return to your application. Architect and our partner FCM, Dorman Trading, are legally required to collect some information about you when opening your account. You will also have a chance to review the various agreements and terms from both Architect and Dorman Trading. As one step in this process, you'll be directed to [Plaid](https://docs.architect.co/architect-user-guide-and-faq/getting-started/onboarding-and-kyc/who-is-plaid) to answer a few identification questions, and returned to continue Architect's account sign-up process afterwards. After completing the onboarding steps, we will promptly process your application. You will receive an email confirmation when your account is open. ## Institutions To open an institutional account, reach out to . There are additional KYC and AML requirements for institutions that cannot be completed online. --- # 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.architect.co/user-guide/getting-started/opening-an-account.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.