> For the complete documentation index, see [llms.txt](https://international.open.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://international.open.gov.sg/welcome-to-ogp-international.md). # Welcome to OGP International Open Government Products (OGP) builds technology for the public good. Our tools are designed by and for government teams, addressing real operational challenges with practical, secure solutions. ### What You'll Find Here #### 🧪 Demos *(Coming Soon)* Experience our products firsthand through live demonstrations. See how government teams worldwide use OGP solutions to improve citizen services and streamline operations. #### :tools: Self-Hosting Guides Deploy OGP products in your own infrastructure with comprehensive guides tailored for government IT teams. From evaluation to production deployment, we provide the technical guidance you need. #### 🔧 Blueprints *(Coming Soon)* Proven patterns and architectural guidance for adapting OGP solutions and practices to your specific government context and requirements. **Ready to get started?** Most teams begin with our demos to understand capabilities, then move to self-hosting guides for implementation planning. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://international.open.gov.sg/welcome-to-ogp-international.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 `build a script that syncs our docs to a CMS` 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.