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

# Surge documentation

Start here to learn how Surge works and create your first strategy.

[1. Welcome to Surge](/tutorials/1.-welcome-to-surge.md) for a short introduction to strategies and non-custodial trading.

Surge is a non-custodial automated trading platform for Cardano. You connect a Cardano wallet, set up a strategy, and Surge watches the market and executes it automatically. Your keys never leave your browser. Every trade is signed there by a wallet only you control, within limits you set.

### Start here

1. Learn [what Surge is](/getting-started/what-is-surge.md).
2. [Connect your wallet](/getting-started/connecting-your-wallet.md).
3. Create [your first strategy](/getting-started/first-strategy-walkthrough.md).

### Before you begin

Two things to know before anything else:

* **Leave the Surge tab open.** Trades are signed in your browser, so a strategy runs unattended for as long as the tab is open and connected — but pauses if you close it. See [How non-custodial works](/getting-started/how-non-custodial-works.md).
* **Trades on Cardano DEXes are not instant.** An order normally takes 1–2 minutes to fill, and on some DEX's an order that cannot fill stays open until you cancel it. See [How trading on Cardano DEXes works](/core-concepts/how-cardano-dex-trading-works.md).

### Need help?

Find answers in the [FAQ](/help/faq.md), resolve problems in [Troubleshooting](/help/troubleshooting.md), or look up terms in the [Glossary](/help/glossary.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.surgecardano.com/readme.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 `build a script that syncs our docs to a CMS` 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.
