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

# Airdrop Overview

**When&#x20;**<mark style="color:green;">**LAB Terminal**</mark>**&#x20;came out of closed beta, we wanted to launch with more than just new features**. \
\
Crypto trading today is fragmented - traders switch between many apps, losing time and money to fees, delays, and clunky tools.\
\ <mark style="color:green;">**LAB**</mark> was built as a layer on top of these platforms, improving what you already use instead of trying to replace it.

With <mark style="color:green;">**LAB Terminal**</mark> you get **faster execution, lower fees, AI-powered trading signals, advanced order types (TP/SL, MEV protection, custom gas), a browser sidebar extension, perpetual futures, and multichain support** (Solana, Base, Ethereum, BSC and more on the way).

#### To mark this launch, we introduce you to the **LAB Loyalty Airdrop**: a two-season rewards program.

{% hint style="info" %}
**Season 1 (Loyalty Airdrop)** — rewards your past trading on external platforms.
{% endhint %}

{% hint style="info" %}
**Season 2 (Trading Airdrop)** — rewards active trading inside LAB Terminal.
{% endhint %}

Both seasons are live now and will run until the **Token Generation Event (TGE)** in **Q4 2025**, when all $LAB rewards can be claimed.


---

# 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.lab.pro/lab-loyalty-airdrop/airdrop-overview.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.
