> For the complete documentation index, see [llms.txt](https://carto.gitbook.io/demos/PWfJD7sBWtlDSScCyqMo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carto.gitbook.io/demos/PWfJD7sBWtlDSScCyqMo/readme.md). # Welcome to the CARTO Demo Hub! **Welcome to the CARTO demo hub!** 👈 Find the best demos for every vertical, use case and cloud on the left. *** ## FAQs 💡 **Top tip!** Replace builder/viewer/map in the demo URL to view the demo in editor/organization/public mode respectively. Some functionality is only available in certain modes - such as AI Agent in organization/viewer mode. Note you will need to be logged in to the relevant organization to access editor/organization mode. **❓ Can I share this?** All demos can be shared far and wide! However, please do not share links to the demo hub externally. **👀 Looking for the old Resource Center?** This was deprecated in May 2025, but you can find a backup of all content from this [here](https://docs.google.com/spreadsheets/d/1me6QkVBdj04wFlp__NW1rd4ZhFFhDhNqNw5qAGE5MGA/edit?gid=1647357229#gid=1647357229). Please note that neither this - nor any demos linked there - are maintained. [**❗**](https://emojipedia.org/exclamation-mark) **Got an issue?** Please contact the creator of each demo, which is listed on the demo page. For wider issues/feedback, please contact product marketing (). [🚀](https://emojipedia.org/rocket) **Created a killer demo that deserves to live here?** Please contact product marketing () with details! --- # 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://carto.gitbook.io/demos/PWfJD7sBWtlDSScCyqMo/readme.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.