> 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/summary.md).

# Documentation overview

Browse the Surge documentation by task and topic.

### Getting started

* [What Surge is](/getting-started/what-is-surge.md)
* [How non-custodial works](/getting-started/how-non-custodial-works.md)
* [Supported wallets](/getting-started/supported-wallets.md)
* [Connecting your wallet](/getting-started/connecting-your-wallet.md)
* [Your first strategy, step by step](/getting-started/first-strategy-walkthrough.md)
* [Run Surge on an always-on computer](/getting-started/run-surge-on-an-always-on-computer.md)

### Core concepts

* [How trading on Cardano DEX's works](/core-concepts/how-cardano-dex-trading-works.md)
* [Supported DEXes](/core-concepts/supported-dexes.md)
* [Wallets in Surge](/core-concepts/wallets-in-surge.md)
* [Signing and approvals](/core-concepts/signing-and-approvals.md)
* [How prices are sourced](/core-concepts/how-prices-are-sourced.md)
* [From decision to confirmation: the trade lifecycle](/core-concepts/trade-lifecycle-and-statuses.md)

### Strategies

* [Choosing a strategy](/strategies/overview.md)
* [Grid](/strategies/grid.md)
* [DCA](/strategies/dca.md)
* [Sequential arbitrage](/strategies/sequential-arbitrage.md)
* [Parallel arbitrage](/strategies/parallel-arbitrage.md)
* [Rule-based](/strategies/rule-based.md)
* [Cadence (Volume)](/strategies/cadence-volume.md)
* [Managing strategies](/strategies/managing-strategies.md)

### Fees, tiers, and staking

* [Fee breakdown](/fees-tiers-and-staking/fee-breakdown.md)
* [The Surge fee and its minimum](/fees-tiers-and-staking/surge-fee-and-minimum.md)
* [Tiers and discounts](/fees-tiers-and-staking/tiers-and-discounts.md)
* [Staking SURGE](/fees-tiers-and-staking/staking.md)

### Orders and transactions

* [Order statuses](/orders-and-transactions/order-statuses.md)
* [Fills and refunds](/orders-and-transactions/fills-and-refunds.md)
* [Cancelling stuck orders](/orders-and-transactions/cancelling-stuck-orders.md)
* [Trade history and activity](/orders-and-transactions/trade-history-and-activity.md)
* [Profit and loss](/orders-and-transactions/pnl.md)

### Dashboard and account

* [Dashboard](/dashboard-and-account/dashboard.md)
* [Portfolio](/dashboard-and-account/portfolio.md)
* [Manual swap](/dashboard-and-account/manual-swap.md)
* [Wallets page](/dashboard-and-account/wallets-page.md)
* [Notifications and alerts](/dashboard-and-account/notifications-and-alerts.md)
* [Settings](/dashboard-and-account/settings.md)

### Help

* [Troubleshooting](/help/troubleshooting.md)
* [FAQ](/help/faq.md)
* [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 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/summary.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.