> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/legal/terms.md).

# Terms of use

The terms that apply when you use kyte.sh.

*As shown on kyte.sh/terms. Last updated 30 October 2026.*

**What Kyte is.** Kyte is a set of smart contracts on Robinhood Chain and a website that helps you interact with them. The contracts hold collateral and settle options. Nobody at Kyte can access, freeze or move your funds.

**Who can use it.** You must be legally allowed to trade options in your jurisdiction. Residents of restricted or sanctioned jurisdictions may not use the protocol. You are responsible for your own compliance and taxes.

**Risk.** Options can expire worthless. Sellers can be assigned at the strike and buyers can lose the entire premium. Listed tokens may be volatile, illiquid or controlled by third parties. Smart contracts can contain bugs. Only use funds you can afford to lose.

**Settlement.** Settlement is physical and enforced by the contracts. A transaction that lands after expiry fails. Exercise well before expiry. Payouts arrive as WETH.

**Fees.** Fees are 3% of the premium when an offer fills and 0.1% of the strike on exercise. They are recorded on each position when it is created and split by the FeeVault contract.

**No advice.** Nothing on this site is investment, legal or tax advice. Kyte does not recommend any position.

**Changes.** Protocol settings change only through a public 10 minute timelock. These terms may be updated; the version on this page applies.


---

# 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.kyte.sh/legal/terms.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.