Skip to content
MadooMadooDocs

AI safety limits

Madoo sets AI safety limits: at most so much AI an organization can use in a day and in a month, and, for some workspaces, a limit of their own. They protect the account — and Madoo — from unexpected spending: a workflow that loops, an embed exposed to the public, a mistake in a batch. They are set by Madoo, not by the customer, and shown only as a percentage of each limit, never as an amount. The day is the calendar day in UTC, the month the calendar month in UTC, from the 1st.

AI safety limits are not usage limits. Usage limits are the customer’s own optional limits in credits; AI safety limits are Madoo’s, and they cover AI generation only. A paid plan’s limit grows with the credits the organization buys, so a customer who buys more can use more.

What pauses, and what keeps working

Section titled “What pauses, and what keeps working”

When an AI safety limit is reached, AI generation pauses until the day or the month resets: workflow steps that use an AI model, the AI assistant and Madoo AI. Everything else keeps working — steps without AI, results already produced, downloads, editing workflows. Credits are not touched: nothing is charged for what was refused.

  • At submission a run with AI steps is refused with 503 ai_spend_paused (AI_SPEND_PAUSED on the internal API). The details (ai_spend on the REST API, the structured content of the MCP error) say reason: "safety_limit" and resets_at, when AI resumes; the response also carries Retry-After in seconds. REST: Executions §1.4; MCP: the execute_workflow error.
  • During a run an AI step that meets the limit fails with AI_SPEND_PAUSED and the message says when AI resumes; the unused credits of the run go back.
  • The same code with reason: "paused" means Madoo has paused AI generation for a moment (for the platform, a plan or this account), with no end given: retry later.

Do not retry in a loop. Tell the person that AI generation is paused until resets_at (shown in their local time), that steps without AI still run, and that if they need a higher limit they can contact Madoo support. Buying credits lifts a limit only when it grows with the credits paid; it never lifts a pause.

How the limits show

Section titled “How the limits show”

In the app, the credit badge at the bottom left shows a row AI today and AI month once a limit is at 80 % or more, with the share used; when one is reached, a card says until when AI is paused. The usage page (Usage → Credits) always shows the share of each limit and when it resets. When a limit reaches 80 %, and when it is reached, Madoo e-mails the organization’s owners and billing contacts — plus the workspace’s admins for a workspace limit — and shows them a notification, once per limit and per day or month.

The limits cannot be read or changed through the public API or MCP. An agent that is refused should report the refusal and when AI resumes, not look for a way around it.