- Home
- Skills
- Agents & Orchestration
- Shared Rate Budget for Multi-Agent Setups
Works with the AI Agents you already use
Shared Rate Budget for Multi-Agent Setups
Run several agents on one account without a rate-limit ban: one shared budget, and a 429 seen by one agent pauses them all.
$15
Shared Rate Budget for Multi-Agent Setups
Example session with this skill installed
I run a scout agent and a posting agent on the same X account from cron, plus an analytics job. We got rate limited last night. Set up pacing so it doesn't happen again.
- Read your context and instructions
- Compiled the shared rate budget
Summary
All three jobs now share one budget for the account, start at different minutes, and a 429 seen by any of them pauses all three.
Setup I ran
python3 scripts/budget.py config x-main --limit 30 --window 3600 --min-gap 20
| Job | Schedule (was) | Schedule (now) | Per-run cap |
|---|---|---|---|
| scout | :00 | :05 | 6 searches (take x-main each) |
| poster | :00 | :25 | 4 replies |
| analytics | every hour | :45 every 3 h | 1 scrape |
Added to each job
export AGENT_NAME=scout
if ! python3 scripts/budget.py take x-main; then
echo "budget says wait; ending run"; exit 0
fi
On any 429 / "try again later":
python3 scripts/budget.py hit429 x-main --retry-after 900 --agent "$AGENT_NAME" && exit 0
Current state
x-main: used 11/30 per 3600s | cooldown 0s | strikes 0 | by agent {"scout": 6, "poster": 4, "analytics": 1}
Next steps
- Keep the limit at 30/hour for a clean week before raising it.
- If
statusshows one job using most of the budget, cut that job first. - Do not log in again or switch accounts after a 429; it is a pacing problem, not an auth problem.
Connects securely to your tools. The creator never sees your data.
About this skill
Outcome: every agent on the account shares one request budget, so a scout, a poster and an analytics job never trip the limit together, and one 429 pauses all of them.
Why this over a prompt rule: "be polite" in a prompt is per agent; the limit is per account. This enforces it in code with a lock file every job must take before it calls the API.
Guaranteed: if it doesn't do what this page says on your setup, message me here or email support@tensorust.com and I fix it.
What it prevents
Rate limits belong to the account, not the agent. Three agents that are each "polite" are still one rude account. Per-agent backoff does not help: while agent A waits, B and C keep spending the same budget, and the platform sees one account hammering it. Retries with jitter spread requests out; they do not reduce them.
The incident behind it (true)
A developer ran three agents on one X account: a trend scout running searches, a writer posting replies, an analyst scraping the account's own stats. Each had its own pacing. One evening X returned 429 Too Many Requests on the account's own endpoints (the calls the site makes on every page load), not just on search. No single agent was over anything it knew about. What fixed it was not smarter retries: pause about 2 hours, stagger the jobs (:05 and :25), cap the scout at about 6 searches per run, let the analyst scrape once, stop reloading pages. The next analyst run scraped 143 rows with no 429. This skill is that fix, enforced by a script every agent calls.
What you get
budget.py(stdlib Python, file-locked JSON ledger per account):config x-main --limit 30 --window 3600 --min-gap 20take x-mainbefore every action: exit 0 = go, exit 3 = WAIT with seconds and reasonwait openai-org --cost 5 --max-wait 120to block up to a caphit429 x-main --retry-after 900: shared escalating cooldown (15 min, 30, 60, 120, capped at 4 h; strikes reset after 24 h clean). Every agent on that account waits.status: usage by agent, so you can see which role is eating the account- Tested with 8 concurrent takers on a 5-request budget: exactly 5 go.
- The rules: one bucket per credential, take before you act, a 429 belongs to everyone, escalate instead of jitter, stagger schedules, count the hidden page-load calls of browser automation, start at about 50% of documented limits, and never switch accounts or keys to get around a limit.
- Copy-paste snippets for shell and Python, and the exact per-run instructions for the agent.
Works for social accounts, LLM API keys shared by parallel workers, scrapers, and any API several cron jobs touch.
Agents must call budget.py before acting; it cannot intercept requests on its own. All agents must share one state directory (same machine or a shared folder).
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires