> For the complete documentation index, see [llms.txt](https://references.everstrike.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://references.everstrike.io/introduction.md).

# Introduction

### What Everstrike is

Everstrike is a decentralized exchange for spot, perpetual futures, and perpetual options.

You write a strategy in plain English. Everstrike evaluates it with AI and can place trades when your conditions are met and the result clears your minimum confidence threshold.

Every strategy evaluation produces an [event](/ai/events.md). Events record the decision, confidence, and trading context behind each action.

Everstrike supports both self-custodied and managed trading flows. In **DEX mode**, you connect your own wallet. In **CEX mode**, Everstrike manages the wallet for you. See [DEX Mode vs. CEX Mode](/account/dex-mode-vs.-cex-mode.md) for the difference.

Everstrike supports [Arbitrum One, Base, Ethereum, and Binance Smart Chain](/account/supported-networks-and-stablecoins.md).

### What vibetrading means

Vibetrading means writing [strategies](/ai/strategies.md) as prompts instead of placing manual orders.

A strategy defines:

* the markets to watch
* the instructions the AI should follow
* the minimum confidence required before trading

You do not need to write code. You do need to set clear instructions, position sizing, and risk limits.

### What to read next

* Start with [How to start trading on Everstrike](/trading/how-to-start-trading-on-everstrike.md)
* Learn how [strategies](/ai/strategies.md) work
* Check [Trading Fees](/trading/trading-fees.md)
* Review [Supported Networks and Stablecoins](/account/supported-networks-and-stablecoins.md)


---

# 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://references.everstrike.io/introduction.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.