Reference
Rate limits
Limits exist to keep one workspace from degrading another, not to meter your usage. There is no volume cap: no request quota, no vote quota, no cap on customer accounts or teammates.
The limits
| Surface | Limit | Applies to | |
|---|---|---|---|
| MCP server | 240 / minute | Per workspace key. Every tool call, read and write alike. | |
| Sign-in email | 5 / hour | Per address, for admins and customers, so an address cannot be used to send mail at someone. | |
| Sign-in from one connection | 20 / 15 minutes | Customer sign-in links asked from one connection, so a whole office can sign in to vote. Admin sign-in links: 8 / 15 minutes. | |
| New request | 10 / 10 minutes | Per customer account. | |
| Vote | 120 / 10 minutes | Per customer account, votes and withdrawn votes together. | |
| Comment | 10 / 10 minutes | Per customer account. | |
| Teammate invitation | 20 / 15 minutes | Per workspace, invitations and resends together. | |
| Announcement emails | 10,000 / month | Per workspace. A ceiling against abuse that an honest board does not reach; write to us if yours gets close. |
Posting, voting and commenting count per customer account, never per connection, so an office behind one address is many people, not one. Crossing a limit answers 429 with a Retry-After header; on the portal, the visitor sees a page asking them to wait a moment.
Staying under them
240 calls a minute is four a second, sustained. Importing a backlog goes well under it if your agent uses import_requests, which takes up to fifty requests in one call, rather than creating them one at a time.
Reading your portal costs nothing against these limits. Only posting, voting, commenting, signing in, inviting and calls made with your workspace key are counted.