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

# Rules and limits

The limits every offer is checked against before you sign.

{% hint style="success" %}
**In short.** Expiry from 1 hour to 90 days, a minimum premium of 0.0005 ETH, per-token exposure caps and minimum strikes, at most 200 open offers per seller per market, and no fee-on-transfer tokens. A pause never blocks an exit.
{% endhint %}

| Rule                              | Value                                                                     |
| --------------------------------- | ------------------------------------------------------------------------- |
| Expiry                            | 1 hour to 90 days from creation                                           |
| Fill deadline                     | In the future, and ≤ expiry                                               |
| Minimum premium                   | 0.0005 ETH (total)                                                        |
| Minimum strike                    | Per token, set in the registry (total strike, in WETH)                    |
| Exposure cap                      | Per token, per market: total underlying in open + filled positions        |
| Open offers per seller            | At most 200 at a time, per market                                         |
| Tokens                            | Only listed and enabled tokens; puts need puts enabled as well            |
| Fee-on-transfer / rebasing tokens | Rejected: the escrow must receive exactly the stated amount               |
| Self-trade                        | You can't buy your own offer                                              |
| Pause                             | Blocks only new offers, fills, new stake and buybacks. Exits always work. |


---

# 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/reference/rules.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.