Glossary · Network & evasion

Cadence governing

Pacing runs per account so one identity is not re-poked faster than a real user would — and backing off after a push-back.

What is cadence governing?

A cadence governor constrains how often one account, on one host, may run: a minimum gap between runs and a cap per rolling window, plus a cooldown stamped after a run ends blocked, rate-limited or challenged. Exceeding a constraint is refused before any credit is reserved, with a retry-after and a machine-readable reason.

Why it matters

This protects the customer’s own account from the target, not the service from the customer — a distinct thing from a service rate limit. It also fails open by design: a pacing safety net that takes runs down harder than the target would have is worse than none.

Related terms

See it in context

Back to the full glossary

Put your agent to work. Keep the decision.

Give your agent a real browser, authorize the accounts it may use, and keep control of every step. Repeated runs compile into skills that replay without a model.