> For the complete documentation index, see [llms.txt](https://ovro.gitbook.io/ovro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ovro.gitbook.io/ovro-docs/resources/brand-kit.md).
# Brand kit
OVRO logo, colors and usage.
## Logo
The mark is a horned owl's head. The two eyes are the O·O of OVRO, and the red pupil marks the winner.
| File | Use |
| -------------------------------------------------------------------- | ------------------------------------ |
| [Logo, light background](https://ovro.fun/brand/ovro-logo-light.png) | Articles, listings, light interfaces |
| [Logo, dark background](https://ovro.fun/brand/ovro-logo-dark.png) | Dark interfaces |
| [Mark, 512 px](https://ovro.fun/brand/ovro-mark-512.png) | Avatars, favicons, small spaces |
| [Token image, 1024 px](https://ovro.fun/brand/ovro-token-1024.png) | Token listings and wallets |
## Colors
| Name | Hex |
| ---------- | --------- |
| Paper | `#F5F5F2` |
| Ink | `#0E0E0C` |
| Signal red | `#C8321F` |
| Mute | `#76766F` |
## Type
[Geist](https://vercel.com/font) Sans for text and numbers, Geist Mono for addresses and data.
## Usage
* Keep clear space around the logo of at least the height of an eye.
* Do not recolor the mark, stretch it, or add effects.
* The red is used sparingly: for the pupil and for live moments.
---
# 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://ovro.gitbook.io/ovro-docs/resources/brand-kit.md?ask=&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.
