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

# What is Premia?

Other than the Premier DeFi Token Options Exchange (DTOX) 🙅‍♂️

To begin, we should make clear the distinctions between the different areas of "Premia", some of which may confuse new users.

#### <mark style="color:blue;">**The Premia Protocol**</mark>

A suite of upgradable smart contracts that together facilitates peer-to-peer market making and trading of options on ERC-20 tokens available on the Ethereum blockchain along with a settlement engine. This can be thought of as the “base” layer.

#### <mark style="color:blue;">**Premia Vault Depot**</mark>

A suite of in-house and third party smart contracts, composed *on top* of The Premia Protocol, that enables additional user functionality such as participation in automated strategies, leverage, and risk management on the Ethereum blockchain.

#### <mark style="color:blue;">**The Premia Interface**</mark>

A web interface that allows for easy interaction with the Premia protocol. The interface is only one of many ways one may interact with the Premia protocol.

#### <mark style="color:blue;">**Premia Governance**</mark>

A governance system for governing the Premia Protocol, enabled by staking PREMIA token and receiving vxPremia.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.premia.blue/what-is-premia.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.