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

# Brand Kit

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

{% file src="/files/rY3nbminto5Qfy3lBtvk" %}

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

{% file src="/files/WzScSpohjumzqVp5p3CH" %}

### Brand Assets & Usage Policy <a href="#brand-assets-and-usage-policy" id="brand-assets-and-usage-policy"></a>

**Logo and Symbol Files**

The official Kleva AI logos and symbols are provided in:

* `KLEVA AI Logo.zip`: full wordmark logo (symbol + logotype)
* `KLEVA AI Symbol.zip`: standalone symbol only\ <br>

**Usage Guidelines**

* Always use the latest files from the official asset packages.
* Maintain original proportions and colors.
* The symbol can be used standalone only after the full brand has been introduced.
* Place logos on clean, uncluttered backgrounds.\ <br>

**Do Not:**

* Recolor, rotate, or animate the logo/symbol
* Use old versions or screenshots
* Overlay with text or graphics
* Apply glow, gradient, or effects without approval

<br>


---

# 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:

```
GET https://docs.kleva.io/brand-kit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.