Usage limits
note
Orchestrate is an Early Access release. Refer to the Early Access disclaimer for details.
The Orchestrate conversational interface processes text in small chunks called tokens, roughly one token per word, though punctuation and spaces also count. Orchestrate tracks token usage to manage how much information you can send to in the chat and how much it can send back.
- Input tokens: Units to measure the amounts of text in your prompt, any data you provide, and the agent's instructions.
- Output tokens: Units to measure the amount of text in the agent's response.
The following table lists token limits that apply to each prompt and response:
Per-Request token limits
| Dimension | Limit | Description |
|---|---|---|
| Input tokens | ~ 200,000 tokens | Total capacity of the user request including goal, clarifications, mode specifications, and Meta Hub glossaries |
| Response tokens | ~ 16,000 tokens | Maximum length of a single Orchestrate reply |
Per-Account rate quotas
Account limitations on tokens refresh after the rolling time window.
| Window | Cumulative Token Count | Notes |
|---|---|---|
| Hourly | 400,000 tokens | Each design session is approximately 200k tokens |
| Daily | 1,000,000 tokens | Approximately 50 solution designs per day |
| Monthly | 20,000,000 tokens | Approximately 1,000 full solution design sessions per month |
