> For the complete documentation index, see [llms.txt](https://docs.stryke.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stryke.xyz/getting-started/what-is-stryke-clamm.md).

# What is Stryke CLAMM

Stryke CLAMM connects people who want to earn from providing liquidity with people who want to buy options. It builds an options market around concentrated liquidity on established automated market makers, including Uniswap v3.

As a liquidity provider, you deposit assets into selected price ranges. Your position can earn swap fees from trading in the underlying pool and premiums from buyers whose options use your eligible liquidity.

As a trader, you buy calls or puts backed by that liquidity. You pay an upfront premium and choose the price level, expiry, and size that suit your position.

The design gives deposited liquidity another use beyond token swaps. Stryke adds the options system while integrating with existing AMM infrastructure.

There are two main ways to use the product:

* **Earn:** provide liquidity, track earnings, claim available rewards, and withdraw available assets.
* **Trade:** buy options, track your positions, and exercise eligible options.

Your returns depend on market activity, price movements, and the terms of your position. Providing liquidity can result in losses, even when your position earns fees or premiums.

[Explore the CLAMM product overview](https://docs.stryke.xyz/products-overview/product-overview).


---

# 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.stryke.xyz/getting-started/what-is-stryke-clamm.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.
