> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/guides/batching.md).

# Auto-batching

When you have many signature requests to land, Andromeda can pack them into the fewest Solana transactions instead of one transaction each. This cuts fees and confirmation overhead.

{% hint style="info" %}
Exact request and response bodies are in the [OpenAPI spec](https://api.andromedainfra.pro/openapi.json).
{% endhint %}

## How it packs

* Up to **64** signature requests per batch.
* Packed greedily into **K** Solana transactions.
* Each transaction is capped at about **1180 bytes** of packed payload and at most **16** entries.

So a batch of 64 small entries might fit in 4 transactions; a batch of 64 larger entries takes more. The response tells you how the entries were assigned to transactions.

## When to use it

* Airdrops, payouts, settlement runs: many independent signatures at once.
* Periodic flushes: collect signature requests over a window, then batch them.
* Anything where per-transaction fees and confirmations dominate your cost.

## When not to use it

* Latency-sensitive single signatures: a batch waits to pack; a single sign goes straight through.
* Operations that must each be in their own transaction for downstream reasons (for example, each one triggers a separate on-chain effect you depend on landing independently).

## Notes

* Use [`Idempotency-Key`](/hub/andromeda/guides/idempotency.md) on the batch submission so a retry does not double-submit.
* Use [Dry-run / Simulate](/hub/andromeda/guides/simulate.md) to estimate compute units before sending a large batch.
* If a dWallet in the batch is behind a policy, that policy still applies to each entry; a batch does not bypass on-chain rules.


---

# 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:

```
GET https://shinkalabs.gitbook.io/hub/andromeda/guides/batching.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.