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

# Airdrop Strategy

We plan to conduct an airdrop for early supporters of Batching.ai. \
As operators of a platform based on AI technology, we will actively support users in voluntarily becoming AI creators and effectively utilizing it through gaming content.

### AIRDROP ALLOCATION

The quantity of the airdrop will be determined based on user activity and pBAT holdings. \
pBAT consists of Drop points and Referral points, with the weight of each point not disclosed.

### AIRDROP ELIGIBLE PARTICIPANTS

Participants can receive the airdrop if they meet any of the following conditions:

① Participants in the airdrop campaign

② Participants and winners of various events

③ Stakers of HAVAH Coin (HVH)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.batching.ai/batchingai/airdrop/airdrop-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.