> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-one-and-moasure-2-series/integrations.md).

# Integrations

Connect Moasure with compatible software and platforms to extend your workflow and make the most of your measurement data.

Choose an integration below to learn how to export, import and use Moasure measurements with supported tools.

***

### Design & CAD Software

#### [SketchUp](/en/moasure-one-and-moasure-2-series/integrations/sketchup.md)

Import Moasure measurements into SketchUp to support 3D design and modelling workflows.

#### [ArcSite](/en/moasure-one-and-moasure-2-series/integrations/arcsite.md)

Use Moasure measurements within ArcSite to create professional drawings and site plans.

#### [MeasureSquare](/en/moasure-one-and-moasure-2-series/integrations/measuresquare.md)

Transfer measurement data into MeasureSquare for estimating and flooring workflows.

***

### Developer & Data Tools

#### [APIs](/en/moasure-one-and-moasure-2-series/integrations/apis.md)

Explore available APIs and integration options for connecting Moasure with custom systems and workflows.


---

# 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.moasure.com/en/moasure-one-and-moasure-2-series/integrations.md?ask=<question>&goal=<user_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.