> For the complete documentation index, see [llms.txt](https://developer.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://developer.sahamati.org.in/no-longer-relevent/buildaathon-2024.md). # BuildAAthon 2024 Sahamati BuildAAthon 2024 is a hackathon organised as a part of our annual Account Aggregator (AA) community event, SamvAAd 2024. The hackathon promises to be an exciting event, with innovative themes, masterclasses led by esteemed industry leaders, and the opportunity to develop cutting-edge solutions for India’s financial ecosystem. Participants will also have the chance to interact with a panel of distinguished judges and compete for exciting awards. The Sahamati BuildAAthon invites participants to leverage the AA ecosystem to build innovative financial products and services. The BuildAAthon is an exciting platform for young entrepreneurs, builders, and technology enthusiasts to envision the future of Open finance in the country. The AA ecosystem is poised to catalyze the next wave of financial innovation and inclusion in India. Don’t miss out on the chance to be part of this movement! More details about the Hackathon are available [here](https://sahamati-buildaathon-2024.devfolio.co). --- # 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://developer.sahamati.org.in/no-longer-relevent/buildaathon-2024.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.