> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/learn.md). # Learn - [Welcome Aboard!](https://rc.sunbird.org/learn/welcome-aboard.md) - [Overview](https://rc.sunbird.org/learn/readme.md): Build live, reusable and trustworthy registries and verifiable credentials — with configuration, not code. - [Why do we need Sunbird RC?](https://rc.sunbird.org/learn/readme/why-do-we-need-sunbird-rc.md): Stand up trusted registries and verifiable credentials quickly — for any domain. - [What Sunbird RC is and what it's not?](https://rc.sunbird.org/learn/readme/what-sunbird-rc-is-and-what-its-not.md): Where Sunbird RC fits — and what you'll still need to build or bring yourself. - [Core Capabilities](https://rc.sunbird.org/learn/readme/core-capabilities.md): What Sunbird RC can do out of the box — with Registry and Credentials, used on their own or together. - [Workflows](https://rc.sunbird.org/learn/readme/workflows.md): How users, issuers, holders and verifiers move through Sunbird RC — from onboarding to verification. - [Possibilities](https://rc.sunbird.org/learn/readme/possibilities.md): Ideas for what you can build with Sunbird RC across education, healthcare, government and employment. - [Adopters](https://rc.sunbird.org/learn/adopters.md): Implementations built on Sunbird RC, and the status of each. --- # 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://rc.sunbird.org/learn.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.