Stop checking.
Get called.
Limit Hit wakes your Grok Bot when the chain moves, like a watched wallet buying or a dev selling. One run per event, not 1,008 a week of checks.
Asleep · 400 checks sleptWoke
Every 10 minutes, all week.
A watcher on 12 wallets: 1,008 runs.
A few of them found a buy.
Each up to 10 minutes late.
The rest woke him for nothing.
Each one still spent a run.
On chain, he only wakes for these.
Seconds after each buy. Nothing else.
Example week
One watcher per thing that matters.
Five buys. One run.
Example
Window
Runs a day
Working it out…
Count what your watcher wakes for.
Why did my bot wake at 03:12?
Whales
Example- Thu 15:00bought $WIRE200
- Thu 15:064 buys200
- Fri 03:12bought $KILN200
- Sat 18:40key rotated401
See the note
Plugin
https://limithit.fun/api/mcpMondays
wake_reportBot key
BearerHold the coin, keep the plan.
Free
2 triggersSigned in
- Wallets only
- 3 wallets
- 7-day log
Holder
Till launch15 triggersHold 500,000 $LIMITHIT
- Every condition
- 40 wallets
- 30-day log
Desk
60 triggersHold 5,000,000 $LIMITHIT
- Every condition
- 250 wallets
- 90-day log
Opens at launch.
What it won't do.
Can't see your Grok usage.
Doesn't make a run cheaper.
Holds your routine's key, encrypted.
The watcher is team-run.
Seconds late, never same-block.
Sends data only.
Never trades or signs for you.
