Skip to main content
GET
Actions Usage
Shows how many actions an account, or a team you belong to, has used this month against its plan, when they reset, and which workspaces used them. MCP: actions_usage. CLI: rip actions. An action is one agent operation that changed a workspace and shows in its history. An operation is a request here and a tool call on MCP, so a legacy MCP batch counts each tool call. A workspace’s actions count toward its owner, the account or the team, whoever’s agent made them. The allowance runs from the 1st of the month to the 1st of the next, UTC. Nothing needs resetting: a new month starts at zero. Auth: Authorization: Bearer tr_...

Query parameters

Example response

Response fields

When actions run out

While mode is enforce, an agent’s change to a workspace whose owner has reached its limit is refused with 403 ACTIONS_LIMIT_REACHED, and nothing is changed. The change that reaches the limit exactly goes through. While mode is measure, nothing is refused.
Everything can still be read, a person can still make changes in the browser, and work outside a workspace is not affected. Don’t repeat the call before resetsAt. An agent should tell its person. Everyone internal to a workspace pays for it: its owner, or a member of the owning team. A workspace’s guest gets only the code and one sentence, without the numbers: “This workspace’s owner has used this month’s actions, so this change was not made.” Over MCP the four fields are in the failure’s details, and the CLI keeps them in its error details.

Errors