> 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/learn/options-beginner/beginner-strategies.md).

# Beginner Strategies

### 📈 Long Call

&#x20;Investors take a long position by buying or holding a call option. This bullish strategy aims to profit from an asset's price increase without owning the asset.

## 🐻 Short Call

Investors take a short position by selling or writing a call option. This bearish to neutral strategy potentially profits from a decline in the underlying asset's price.

## 📉 Long Put

&#x20;Investors take a long position by buying a put option. This bearish strategy aims to profit from a decline in the underlying asset's price.

## 🐂 Short Put

Investors take a short position by selling a put option. This bullish-to-neutral strategy potentially profits from a rise in the underlying asset's price.


---

# 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/learn/options-beginner/beginner-strategies.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.
