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

# Brand and links

Official channels, the name, and the visual identity.

## Official channels

| Channel | Address                              |
| ------- | ------------------------------------ |
| Website | [miragefi.org](https://miragefi.org) |
| X       | [@MirageFi](https://x.com/MirageFi)  |
| Contact | <hello@miragefi.org>                 |

No other domain or handle that claims to be MirageFi is genuine. Contract addresses will be published only on this documentation site and on the website, never anywhere else.

## Name

The name is written **MirageFi**, with a capital M and a capital F, never in all caps in running text.

## Voice

Product and documentation share one voice: calm, technical, precise. Sentences are short and declarative, numbers come with their units, costs are itemised instead of summarised, and risks appear in the reading path rather than in footnotes. There is no hype, no exclamation mark and no manufactured urgency. Any sentence that would not stand up to being read back by a sceptical auditor is rewritten until it does.

## Visual identity

The mark is a layered cloud: overlapping translucent sheets in aqua, mint and periwinkle that combine into a single shape. On the site it rests above a desert scene: warm sand for the ground and the surfaces, a sheet of crystal water along the horizon at the point where a mirage would form, and a low sun. The image stands for many sources of liquidity resolving into one clear price, which is what the venue does.

### Palette

| Token       | Hex       | Use                                   |
| ----------- | --------- | ------------------------------------- |
| Ink         | `#241c14` | Headings and body copy                |
| Slate       | `#4f4233` | Secondary copy                        |
| Muted       | `#74675a` | Supporting copy                       |
| Faint       | `#a2958a` | Labels and timestamps                 |
| Sand        | `#faf5ec` | Page background                       |
| Paper       | `#fffdf9` | Cards and sheets                      |
| Dune        | `#efe5d2` | Tinted surfaces and skeletons         |
| Aqua        | `#0b8f9a` | Primary actions and positive status   |
| Aqua bright | `#3ed2dc` | Gradients on buttons and headlines    |
| Lagoon      | `#1670a8` | Links, eyebrows and accent panels     |
| Shallows    | `#5cc8e3` | Markers and extended-session segments |
| Sun         | `#b47d1c` | Third accent and warnings             |
| Terracotta  | `#c4542e` | Loss figures and errors               |

### Type

* Headings: Fraunces at optical size 144 in the regular weight, with italics for emphasis within a headline
* Body: Inter
* Labels and figures: JetBrains Mono, set in small caps with wide tracking

### Usage

* Place the mark on a pale sand or paper background only. Never set it on saturated colour.
* Do not recolour the mark or apply effects to it; the layered sheets are the mark itself.
* Keep clear space around the mark of at least half its width.
* The water colours belong to things that act or signal (buttons, links, status). Sand and paper belong to surfaces. Do not exchange the two.


---

# 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.miragefi.org/resources/brand.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.