> 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/developers/apis/clamm-deprecated/strikes-chain.md).

# Strikes chain

The `/strikes-chain` endpoint retrieves the options chain, also known as the strikes chain, providing information about each strike price, along with additional details regarding handlers and hooks. This endpoint offers a comprehensive view of available options for a given market, including where the liquidity for each strike comes from and the specific conditions under which it can be used.

### How Handlers and Hooks Work

* **Handlers** specify the DEX and the specific liquidity pool from which the liquidity for the options is sourced. This information is useful for understanding the underlying structure supporting the options market.
* **Hooks** outline constraints such as the maximum allowable duration for which the liquidity can be utilized (Time-To-Live or TTL) and the expiration conditions for the options.

Together, handlers and hooks provide a deeper understanding of the liquidity and constraints governing the options chain.

{% openapi src="/files/uiLe2AdTixay9Y0zMePt" path="/clamm/strikes-chain" method="get" %}
[stryke-api-swagger.yaml](https://1713171471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtOz5vakeeIFF4xdhXZoK%2Fuploads%2F7vSesYn9AbVPrQsNonoy%2Fstryke-api-swagger.yaml?alt=media\&token=3587d8b1-a932-4855-978d-363671da0ce2)
{% endopenapi %}


---

# 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/developers/apis/clamm-deprecated/strikes-chain.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.