> For the complete documentation index, see [llms.txt](https://docs.gammaswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gammaswap.com/introduction.md).
# Introduction
An overview of the V2 exchange
## What is GammaSwap?
GammaSwap is a high performance prediction market focused on financial assets. Users can predict whether cryptocurrencies like BTC and ETH will be up or down over short timeframes (5 minutes, 15 minutes, etc) while maintaining custody of their assets. It was engineered from the bottom up to be fast, simple and efficient.
### Key Aspects of GammaSwap
* **Non-Custodial.** You maintain full control of your assets.
* **Margin Based.** Simple and capital efficient.
* **Instant Resolutions.** No human intervention needed.
* **Off-Chain Matching.** Low latency performance.
* **On-Chain Settlement.** All matched trades settle on-chain and are public.
### High Level Exchange Mechanics
The exchange matches orders off-chain and sequences the transactions that ultimately settle on [Base](https://www.base.org/), a layer 2 blockchain created by [Coinbase](https://www.coinbase.com/).
Blockchain interactions are abstracted away for the user. They do not need gas to deposit or submit orders. Instead, the exchange pays gas on their behalf.
After signing to deposit, all trades can be performed without wallet pop ups mimicking a traditional trading experience.
---
# 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.gammaswap.com/introduction.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 `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.
