## TL;DR

Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. The practical consequence: chunk keyword lists into groups of 100 per POST and throttle to stay under the per-minute ceiling.

## Steps

1. Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. The practical consequence: chunk keyword lists into groups of 100 per POST and throttle to stay under the per-minute ceiling. Oversized batches do not queue gracefully - split them client-side before sending.

## When to use

You are seeing this: Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. Use this skill when you run into "100 tasks per POST, 2000 calls per minute - chunk batches client-side".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.