> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/integration/guideline.md).

# Trybit Brand Guide

The Trybit brand guide is designed to make things easier for everyone who interacts with our brand and provides clear instructions for logos, color palettes, typography, and web components such as payment method designations and payment buttons.

<div data-full-width="true"><figure><img src="/files/0m4RWYq1sBTK4W4DsDra" alt=""><figcaption></figcaption></figure> <figure><img src="/files/mZCn5PozVHX3qUAYVnUX" alt=""><figcaption></figcaption></figure></div>

* Brand elements — everything you need to know about using the logo, buttons, icons, and other elements.
* Marketing materials — everything you need to know about promoting cryptocurrency payments on your website.

Using the Trybit brand book builds customer trust, increases loyalty, and ultimately drives growth in key business metrics such as conversion rates, average order value, and repeat purchases.

Learn more about how to use the guideline in the section.

{% hint style="info" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% endhint %}


---

# 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://support.trybit.com/integration/guideline.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.