> For the complete documentation index, see [llms.txt](https://docs.buildingtransparency.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildingtransparency.org/ec3/integrations.md).

# Integrations

EC3 has working integrations with top design and construction-related software to create an ecosystem of aligned and harmonized solutions.

Our open digital EC3 database is leveraged by other technology providers in the industry, enabling the carbon data of materials to be part of the decision-making process within the tools already broadly used by building and infrastructure professionals.

Here are some of our main integrations and partners.

* Tally - see [user guide](https://app.gitbook.com/o/bfOTgYn0LuJrbcRYg4Le/s/PDhVD99RBnS0Qy4HvVPO/~/edit/~/changes/255/ec3/integrations/tally)
* Autodesk Construction Cloud - see [user guide](/ec3/integrations/autodesk-construction-cloud.md)
* Bentley iTwin Systems - see [user guide](/ec3/integrations/bentley-itwin-systems.md)
* Procore - watch [video tutorial](https://youtu.be/_Dlnc4zCZOc)
* Transparency Catalog - watch [video tutorial](https://transparencycatalog.com/blog/for-manufacturers-introducing-transparency-catalog-project-builder-library)

While we don't control all integrations with other platforms, we see ourselves as a part of a broader AEC ecosystem and collaborate with other providers aligned with our mission. If you have a third party platform that you woul like to integrate with EC3, let us know.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildingtransparency.org/ec3/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.