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

# Introduction

### Welcome to ClickOptions

ClickOptions is a crypto options venue built for better pricing (Flow-Implied pricing), deeper markets (coordinated liquidity across strikes/expiries), and clearer decisions (timestamped spread/depth benchmarks). Our goal is simple: help you trade volatility, not friction, with transparent methods and fair-play rules.

#### Who this documentation is for

**Traders**: instruments, fees, order types, risk controls, settlement.

**Liquidity providers**: incentives, penalties, and onboarding.

**Institutions**: connectivity, custody, reporting, SLAs.

**Builders**: APIs, market data, SDKs, sandboxes.

**Community**: programs, referrals, education, policy.

#### How to use these docs

**Trade:** Everything needed to place and manage orders: accounts and funding, instrument specs, order types and matching, market microstructure/risk controls, and index/settlement methodology. Start here if you’re trading.

**Earn:** Vaults and staking mechanics, token utility/policy, affiliate and referral, and MM/LP program details.

**Trust:** Security and custody, audits/reports, pricing and spread benchmarks (method + monthly report), status/incidents, legal/compliance, privacy/data.

#### Conventions and support

**Dated pages**: Look for “Last updated” to confirm recency; benchmark cards will be timestamped with a method footnote.

**Need help?** Join our official channels.

Welcome. Let’s make options cheaper, tighter, and clearer. Together.


---

# 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.clickoptions.ai/introduction.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.