> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/media/logos-and-assets.md).

# Logos & Assets

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

When integrating OISY, please use one of the logos from this archive: &#x20;

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

***

For most dApp integrations, we recommend using the following icon in SVG or PNG format:

<figure><img src="/files/Mpa9UBQtpqIyQO7UEmSk" alt="" width="160"><figcaption><p>OISY icon</p></figcaption></figure>

{% file src="/files/AJV55PvsM7a7v02Kq9Bs" %}
SVG logo version
{% endfile %}

{% file src="/files/Mpa9UBQtpqIyQO7UEmSk" %}
PNG logo version
{% endfile %}

## Brand color

<table data-header-hidden><thead><tr><th></th><th width="249"></th></tr></thead><tbody><tr><td><h3>#0066FF</h3><p>Whenever possible, use this exact hex value to maintain visual consistency across integrations.</p></td><td><img src="/files/FoPtYZEQjErH8ibDanBl" alt=""></td></tr></tbody></table>

***

## "Connect with OISY" Button Guidelines

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

Buttons are a core interactive element and often the first user interaction with OISY.\
Always align them with the OISY brand identity and apply consistently across all platforms.

### Button text

Use the full name with correct capitalization: “**OISY Wallet**”.

**✅ Good examples:**&#x20;

* "Connect with OISY Wallet"
* "Connect OISY Wallet"
* "OISY Wallet"

**❌ Avoid partial names and inconsistent capitalization:**

* "Oisy"
* "Connect with Oisy"
* "Connect Oisy Web Wallet"&#x20;

### Colors & Icons

* Primary brand color: **#0066FF**
* Alternative: approved monochrome variations only
* Avoid using random colors

<figure><picture><source srcset="/files/X7BfS8mkVBJ7Y5fYFdop" media="(prefers-color-scheme: dark)"><img src="/files/KGHpM4AAJYG7YOae0vpy" alt=""></picture><figcaption></figcaption></figure>

### Button icons

Please use the following icons:&#x20;

{% file src="/files/2nMjgsOwgMkS8BkbDgmx" %}

### Spacing & Layout

* Maintain clear padding around text and icons
* Avoid tight or compressed spacing
* Icon must not overlap or touch text

Below you can find examples of the buttons that you should avoid using

<figure><picture><source srcset="/files/9qFgVdzJqntYiqGqoFTy" media="(prefers-color-scheme: dark)"><img src="/files/8WZKaCrFyKyUJhhas4DR" alt=""></picture><figcaption></figcaption></figure>

### tldr: Developer Notes

* Use consistent capitalization: always **OISY Wallet**
* Apply brand color #0066FF or monochrome only
* Ensure readable contrast (WCAG AA minimum)
* Keep minimum 16px padding inside the button
* Do not abbreviate or shorten the product name

**Thanks!**&#x20;

For more info please reach out to: [Support](/using-oisy-wallet/support.md)


---

# 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.oisy.com/media/logos-and-assets.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.