> For the complete documentation index, see [llms.txt](https://docs.metatrust.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metatrust.io/getting-started/getting-started-with-metascan/set-up-an-integration-optional.md).

# Set Up an Integration (Optional)

{% hint style="info" %}
This step can be skipped if you plan to scan code in a public repository or in an uploaded zip-file.
{% endhint %}

## Integration Types

Users can set the appropriate source code platform where the projects to be scanned are located.

## Example: Setting up source code management integration

If you want to scan projects in Git's source code platform, you will need to use Git Repository Integration to connect. MetaScan has pre-built integrations for GitHub, with subsequent extensions for other repositories GitLab, Bitbucket, etc.

**First**, after the user logs in successfully, click \[Integrations] to enter its main interface.

<figure><img src="/files/BrzDjuxgEXg6Fn9ttkSL" alt=""><figcaption></figcaption></figure>

**Next**, click on the source code platform (e.g., GitHub) to integrate with MetaScan.

**Finally**, to grant MetaScan access to the source code platform, enter your account credentials and save your information when prompted.


---

# 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.metatrust.io/getting-started/getting-started-with-metascan/set-up-an-integration-optional.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.