> For the complete documentation index, see [llms.txt](https://docs.bitbond.com/asset-tokenization-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitbond.com/asset-tokenization-suite/token-tool/airdrop-tokens.md).
# Airdrop Tokens
The Airdrop and Multisend Tool offers a streamlined solution for distributing tokens or cryptocurrencies to multiple recipients in a single transaction. Whether you're conducting a manual airdrop to engage your community or rewarding token holders through automated distributions, this tool provides flexibility and efficiency. You can easily multisend any supported assets, taking advantage of three airdrop features to ensure seamless and precise token distribution. The three features consist of:
1. **Custom recipients:** Manually specify recipient addresses and amounts.
2. **Autofill recipients: equal amounts:** Get recipient addresses automatically based on their holdings of a token - each address receives the same amount.
3. **Autofill repients: proportianal amount:** Get recipient addresses automatically based on their holdings of a token - each address receives an amount proportional to their token balance.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bitbond.com/asset-tokenization-suite/token-tool/airdrop-tokens.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
