> For the complete documentation index, see [llms.txt](https://membersuccess.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://membersuccess.sahamati.org.in/member-success/getting-started-with-sahamati.md). # Getting Started with Sahamati ## Overview This document is designed to help Regulated Entities (REs) get started with Sahamati and the Account Aggregator (AA) ecosystem. Whether you are exploring participation or preparing to initiate onboarding, this page provides a starting point to understand what is required and how to proceed. ### Your journey with Sahamati As a Regulated Entity (RE), your engagement with Sahamati begins with preparing for onboarding by understanding the requirements and readiness criteria, followed by completing the onboarding process and gaining access to core ecosystem components such as the Central Registry (CR) and Tokenizer. As you move forward, the Member Success function supports you through ongoing operations, including addressing queries related to Sahamati’s services, enabling participation in ecosystem reporting, facilitating resolution of inter-member issues where required, and supporting your engagement with Sahamati’s membership initiatives and broader ecosystem participation. --- # 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://membersuccess.sahamati.org.in/member-success/getting-started-with-sahamati.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.