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

# Grix Trading Arena

The Arena is a layer designed for user interactions and includes the UI, API, and the Grix intent trading system for DeFi options. Its goal is to provide the user an easy gateway to view the current market, explore different strategies, price quotes, and place orders.

The Arena, as the primary interface for users, aims to offer an optimal experience in trading, hedging, and managing DeFi options positions all in one place.

Part of the advantages in the Grix Arena are the advanced trading features that bring DeFi users an edge versus trading on an underlying options protocols. Limit orders, spread strategies, and more [<mark style="color:purple;">exotic options strategies</mark>](/grix/educational-resources/basic-options-strategies.md) can be traded in one transaction through Grix. There are some complexities needed to be addressed in the basic interface of a user trading a limit order on options, since options decay over time (theta decay), the user experience must be similar to a traditional exchange and must include the greeks originating from the [<mark style="color:purple;">Black-Scholes model</mark>](https://en.wikipedia.org/wiki/Black%E2%80%93Scholes_model).

<figure><img src="https://content.gitbook.com/content/n3odl4ymHi6P7lINhkcx/blobs/CQLfpYFtNSI4c4iIyp9J/Grix%20Arena.png" alt=""><figcaption><p>The Grix Arena</p></figcaption></figure>


---

# 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://docs.grix.finance/grix/grix-protocol/grix-trading-arena.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 `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.