> For the complete documentation index, see [llms.txt](https://docs.adasinnovative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adasinnovative.com/documentation/getting-started/introduction.md). # Introduction ## CarbonSight CO₂ emissions intelligence for ecommerce — deployed into your own Google Cloud project. CarbonSight runs as a Compute Engine VM inside your own GCP project via GCP Marketplace. Your data never leaves your infrastructure. ### What it does * Track Scope 1, 2, and 3 CO₂ emissions per product and category * Visualise 12-month emissions trends * Model green interventions with the built-in simulator * Export compliance-ready PDF and Excel ESG reports * Full BigQuery access — query and modify your data directly ### Support Email: Tickets: adasinnovative.freshdesk.com --- # 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://docs.adasinnovative.com/documentation/getting-started/introduction.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.