Everything you need to know about the "Usage Cap" System
This document details the mechanics of our compute quotas, ensuring consistent availability across the global network.
Encountering a limit on your daily usage can sometimes feel restrictive, but it is a vital mechanism designed to protect the ecosystem. Just like a physical highway can only handle a certain number of vehicles before traffic grinds to a halt, our servers can only process a specific volume of simultaneous automation requests before performance degrades. This guide will walk you through exactly how our metering works, why these boundaries exist, and how you can effectively monitor your daily resource consumption.
1.0 Understanding the Metering Logic
The Usage Cap is monitored in real-time through the Activity module located within the General tab. This interface provides a transparent, visual representation of your daily resource consumption against your tier’s standard allocation. You can think of it like a highly precise digital stopwatch.
Each time a protected asset is active, the server tracks this time with high precision. The moment your automation sequence begins, the server starts counting. The moment it pauses, the server stops. This ensures that you are only ever "billed" for the exact fractions of time you are actively utilizing our processing power, preventing accidental waste of your daily limits.
> ACTIVITY_MONITOR: SYNCHRONIZED
Current Temporal State: 0h 0m
Daily Threshold: / 4h limit
This diagnostic output represents the interface state when the user has not yet consumed resources for the current 24-hour cycle.
Ref: Activity Module UI
2.0 Tier Differentiation: Standard vs. Premium
Because different users have radically different operational needs, the infrastructure separates resource pools based on account tier. Standard users are provided with a generous daily window to complete typical tasks, while Premium users are granted an unrestricted bypass to support massive, industrial-scale automation workloads.
| Tier Profile | Allocation | Reset Cycle |
|---|---|---|
| Standard (Free) | 4 Hours Daily | Rolling 24-hour window synchronization. |
| Premium | Unlimited | Unrestricted infrastructure access. |
3.0 Enterprise Stability Guarantee
The Compute Quota system acts as the primary mechanism for maintaining infrastructure balance, ensuring our REST APIs remain globally responsive. If you have reached your cap, you might wonder why the system simply stops responding rather than slowing down.
Standard Usage Pause: When a Standard user reaches their 4-hour allocation, the backend issues a standard HTTP 429 directive, safely resting the local session until the next cycle resets. Think of this HTTP 429 directive like a traffic light turning red. It is an intentional, protective block that prevents your client device from hopelessly knocking on a closed server door, which saves your local battery and prevents server gridlock.