Rate limits and credits
How many calls a key and a workspace may make, and which calls cost credits.
Rate limits
The limits protect the service from runaway loops. They are not your plan's allowance. MCP and REST calls count together, because they are the same calls.
| Per minute | Per day | |
|---|---|---|
| Each key | 60 | 2,000 |
| Each workspace, all keys together | 120 | 4,000 |
Over a limit, the call gets 429 with a Retry-After header, and nothing runs. Many failed key attempts from one address also get 429 for ten minutes.
Credits
Most endpoints are free: they read data we already store, or save a draft.
- Every call to
refresh_voice_profile,propose_series,generate_videocosts credits, so the key needs thespendscope. scan_reply_targets,get_mentions,get_feed,get_notifications,get_trendsserve stored data for free. A fresh read on a network that bills us (for example X) costs credits and needsspend.- A call that would cost more credits than the workspace has is refused before it starts, and nothing is spent. The brand's monthly spend budget applies too.
Every credit spent shows on Usage, one band per key, for MCP and REST calls alike. See Pricing for what credits cost.