# Media Kit

### Brand Resources

Origin’s visual identity is built around clarity, composure, and institutional credibility. These assets help ensure consistency across media coverage, integrations, and partner communications.

For complete standards and downloadable assets, refer to the **Origin Brand Guide**.

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

#### Primary Logos

Use the **Origin Protocol wordmark** when referencing the company. The blue wordmark should be used when clarity and hierarchy allow. Black or white variants may be used depending on background contrast.

The **Origin symbol** may be used in environments where the brand context is already established, such as documentation, social profiles, or partnership graphics. The symbol should always appear in Origin Blue and remain inside its square container.

Use **product wordmarks** when referencing individual products such as OETH, Super OETH, OUSD, OS, and ARM.

#### Color and Typography

Origin Blue is used **sparingly for emphasis**, while off-black backgrounds and neutral greys form the foundation of the visual system.

Typography follows a simple hierarchy:

* **IBM Plex Sans** for headlines
* **Inter** for body text

#### Token Naming

Token symbols follow consistent formatting:

* OUSD, OETH, and OGN are written in **all caps**
* Staked, wrapped, and super variants use lowercase prefixes (for example: xOGN, wOETH, superOETH)

#### Partnerships & Integrations

When displaying Origin alongside partner logos:

* Maintain equal visual weight between logos
* Preserve clear spacing between brands
* Use Origin Blue selectively to represent the Origin brand


---

# Agent Instructions: 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.originprotocol.com/resources/media-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.