> For the complete documentation index, see [llms.txt](https://docs.degenarena.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degenarena.app/opening-a-position.md).
# Opening a Position
Once you've funded your account with USDT, you can immediately open a long or short position by messaging @degenarenabot.
Let's demonstrate how to open a 25x INJ long position, with 50 USDT margin.
The quick way: message @degenarenabot `/long INJ 25x 50` and click Confirm.
If you want to see all the options available to you, take the scenic route. First, message `/long` to the bot.
Reply with the ticker. For convenience, you can reply `INJ` instead of `INJ/USDT PERP` and the bot will know what you're referring to. As Degen Arena currently only supports perpetual futures, it won't get confused.
Choose your margin by entering an amount or clicking one of the available options from the prompt. In this case, we'll choose 25x.
You'll then be prompted for the amount of margin you'd like to use. Let's use 50 USDT. Don't worry about gas, we've got you covered.
Click "Confirm" and wait for the position to be opened.
Just as quickly as the position is opened, you'll receive a graphic like this from the bot, and if you're part of a group it will also be sent to that group. Because trading is more fun when your friends hold you accountable.
---
# 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.degenarena.app/opening-a-position.md?ask=&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.
