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

# About Arrow Markets

## Overview

In the traditional options market, options must be sold by a writer who receives the premium from the buyer and is responsible for paying the buyer if the option is exercised in the money. As an options protocol on [<mark style="color:purple;">Avalanche</mark>](http://avax.network/), **Arrow Markets** gives users the ability to buy options without the need to be matched by a middle-man. Arrow will facilitate the creation and settlement of options on popular underlying assets such as AVAX, ETH, and BTC.&#x20;

### Namesake

The name *Arrow Markets* is a nod to Nobel laureate economist Kenneth Arrow, who showed that options contracts form a basis for prices and payoffs of financial assets. Options make it possible to construct a wide variety of derivatives and structured products, by forming specific portfolios.


---

# 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.arrow.markets/arrow-markets/welcome/about-arrow-markets.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.