> For the complete documentation index, see [llms.txt](https://docs.tap-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tap-protocol.com/functions/publish-your-docs/mass-send.md).

# Mass Send

{% hint style="info" %}
Tappable
{% endhint %}

Enables mass-transfer of different tokens to many recipients:

* Users inscribe a "token-send" inscription to their Bitcoin address.
* After the transaction confirmed, the inscription has to be resent to the same address for confirmation (tapping).
* Upon tapping, the Bitcoin address must own the the amounts of tokens that are given with the inscription.
* Only if the "token-send" inscription is tapped, sending tokens will be performed.
* The receiver addresses must be carefully validated: must be valid Bitcoin addresses, must be trimmed, addresses starting with bc1 have to be lowercased.
* "token-send" is atomic upon inscribing (before tapping): all amounts, tickers and addresses must be syntactically valid.
* Upon tapping, invalid and semantically incorrect token sends must be skipped (e.g. insufficient funds, invalid amounts or invalid data types).
* Each successful token send must credit the given amounts to recipient and be removed from the sender's balance.
* Each send item must exclusively operate on available balances, not overall balances (available = balance - transferable).

```json
{
  "p" : "tap",
  "op" : "token-send",
  "items" : [
     {
      "tick": "-tap",
      "amt": "10000",
      "address" : "bc1p9lpne8pnzq87dpygtqdd9vd3w28fknwwgv362xff9zv4ewxg6was504w20"
     },
     {
      "tick": "tap",
      "amt": "10000",
      "address" : "bc1p063utyzvjuhkn0g06l5xq6e9nv6p4kjh5yxrwsr94de5zfhrj7csns0aj4"
     }
  ]
}
```


---

# 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.tap-protocol.com/functions/publish-your-docs/mass-send.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.