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

# Introducing Stryke

Stryke is an onchain options platform on Robinhood Chain. It makes options simple on both sides of the trade: buy calls and puts backed by onchain liquidity, or earn by providing the liquidity that backs them.

## Start here

* **Understand the product.** [Product Overview (CLAMM)](/products-overview/product-overview-clamm.md) explains how trading and liquidity work.
* **Trade options.** Buy calls and puts around the current price, then track or exercise your position. See [For Option Traders](/products-overview/product-overview-clamm/for-option-traders.md).
* **Provide liquidity and earn.** Deposit into a price range and earn swap fees plus option premiums as traders buy against your liquidity. See [For Liquidity Providers](/products-overview/product-overview-clamm/for-liquidity-providers.md).

## Earn with SYK and sykASH

Two tokens sit across the platform, funded by trading fees:

* **$SYK:** stake it to earn a share of platform fees. Stakers get 60% of those fees and can convert their share into tokenized stocks. See [SYK Token](/tokenomics/syk-token.md).
* **sykASH:** earned when you take trading losses, with 20% of fees going to holders. See [sykASH](/tokenomics/sykash-token.md).

See [Protocol Fees](/tokenomics/protocol-fees.md) for how fees are split.


---

# 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/introducing-stryke.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.