> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/tools/advanced-settings/vendor-settings.md).

# Vendor Settings

In JENTIS, every tool needs to be assigned to a vendor. By default, each tool has an equivalent vendor with the same name. However, you can create custom vendors with different settings and map your tool to your preferred vendor. This way, you can have more control over the tool-vendor mapping.

Further, a vendor, based on its configuration, can be connected to a CMP (consent management platform) to receive consent information and operate based on the consent provided. For more information on this topic, please refer to <a href="/pages/hWSDQWo0hTYN27FXSsXh" class="button secondary" data-icon="circle-nodes">JENTIS CMP Connectors</a>


---

# 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.jentis.com/jentis-dcp-elements/tools/advanced-settings/vendor-settings.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.
