> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-scanner-cli/xygeni-cli-overview/xygeni-cli-authentication.md).

# Xygeni CLI Authentication

Xygeni CLI uses two types of authentications.

1. **Authentication with Xygeni**

   Xygeni CLI needs to authenticate against the Xygeni platform in order to upload the results found during the different scans. To do it, you need to provide a Xygeni token. Please see [CLI authentication with Xygeni ](/xygeni-scanner-cli/xygeni-cli-overview/xygeni-cli-authentication/cli-authentication-with-xygeni.md)for further details.
2. **Authentication with SCMs, CI/CD platforms and Container Registries**

   Some scan types (CI/CD misconfigurations, for example) need to connect to 3rd party platforms (SCMs, CI/CD, etc.) to gather information and find security issues. To do it, Xygeni must be provided with authentication tokens. Please see [SCM, CI/CD and Container Registry tokens ](/xygeni-scanner-cli/xygeni-cli-overview/scm-ci-cd-and-container-registry-tokens.md)for further info on supported platforms and how to provide those tokens to Xygeni CLI.


---

# 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.xygeni.io/xygeni-scanner-cli/xygeni-cli-overview/xygeni-cli-authentication.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.