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

# Welcome to Stryke

Stryke is a suite of onchain options products. Each one gives you a different way to trade on what happens next to an asset's price, or to earn from the people who do.

Every Stryke product runs on Robinhood Chain and shares the same token layer: **SYK**, **sykASH** and the protocol fees that fund them.

## Our products

### Stryke App

The simplest way to trade options. Choose how much to spend, whether the price will go up or down, and when. The most you can lose is what you pay. Market makers compete to price every trade.

[Get started with Stryke App →](https://docs.stryke.xyz/stryke-app/stryke-app.md) · App: [app.stryke.xyz](https://app.stryke.xyz/)

### Stryke CLAMM

Options built on concentrated liquidity. Liquidity providers deposit into price ranges and earn swap fees and option premiums. Traders buy calls and puts backed by that liquidity.

[Get started with Stryke CLAMM →](https://docs.stryke.xyz/stryke-clamm/stryke-clamm.md) · App: [clamm.stryke.xyz](https://clamm.stryke.xyz/)

## Which product is for me?

|                        | Stryke App                                              | Stryke CLAMM                                              |
| ---------------------- | ------------------------------------------------------- | --------------------------------------------------------- |
| **Best for**           | Trading a price view with limited risk, in a few clicks | Earning from liquidity, or trading the full options chain |
| **What you can do**    | Buy calls, puts and spreads                             | Provide liquidity, buy calls and puts                     |
| **How prices are set** | Market makers quote each trade (RFQ)                    | Black-Scholes pricing, backed by CLAMM liquidity          |
| **Pay with**           | USDG on Robinhood Chain or USDC on Arbitrum One         | The tokens of the market you choose                       |
| **Markets today**      | BTC and ETH                                             | Supported CLAMM pools                                     |

## Shared across Stryke

* [Tokenomics](https://docs.stryke.xyz/tokenomics/tokenomics.md): how platform fees flow to SYK stakers, sykASH holders and the protocol.
* [SYK Token](https://docs.stryke.xyz/tokenomics/syk-token.md): staking for a share of platform revenue.
* [sykASH](https://docs.stryke.xyz/tokenomics/sykash.md): loss rewards that share protocol revenue.
* [Glossary](https://docs.stryke.xyz/references/glossary.md): the terms used across these docs.

Options and liquidity provision carry risk. Options can expire worthless, and liquidity positions can lose value even when they earn fees or premiums.


---

# 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/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 `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.
