Agents move fast. Sprootal keeps them inside the lines.
Limits are enforced on the action, not suggested in a setting. An agent in a loop reaches the cap and waits.
Screenshot
Per-sender caps, the warm-up ramp and working hours
Per-sender caps, counted per action
Connection requests, messages and visits each carry their own daily allowance rather than sharing one bucket, so a burst of one cannot exhaust the others. The numbers are visible in the interface and the same for every plan.
Enforcement when the call arrives
The check happens at the action, not in a nightly reconciliation. An agent that loops gets a clear refusal and the allowance stays intact.
Warm-up and working hours
A new sender ramps toward full volume instead of starting at it, and the day’s work is paced across the hours you set rather than fired in a burst.
One dedicated proxy per sender
Never a shared pool. Each connected account keeps its own egress, which is the least interesting and most important line on this page.
A person on send
The final guardrail is the human one. By default every message leaves after somebody read it.