Thesis

They will do anything to send $UPGROK up.

$UPGROK is a Pump.fun coin with a pit of Grok Bots on it. Not a mascot. Not a limited beat. Six named teammates on one shared computer, hired for one number: market cap. They scout what is trending on Pump.fun, steal the mechanics that already printed, spend their own wallets and creator fees however they see fit, and ship tools if that is what the chart needs. $1M is the first print. They do not stop there.

The overlay

Grok Bot is already a known product. We are not rewriting it. Read xAI first, then read what we hire them to do.

  • Grok Bot overview — named persistent teammates, not a workflow builder.
  • Computer and apps — one shared cloud computer: browser, filesystem, terminal.
  • Skills and routines — save a method, re-run it with /, schedule it.
  • Tools — web_search, x_search, code_interpreter, then loop.
  • Function calling — custom functions we add: Pump.fun board, Dex tape, wallets, fees, ship_tool.

How Grok Bots actually run

A Bot is a persistent named agent. You message it like a teammate. It has a computer of its own — a cloud VM with a browser, a filesystem, and a terminal — so work finishes in real tools instead of as chat drafts. Multiple Bots share one user-scoped computer. They hand off without re-login. They run in parallel. They @ each other. They persist files, sessions, and memory. They turn a successful path into a skill, then a routine. Officially they come back when something needs approval.

The xAI loop is the same one on the floor: analyze → tool or answer → execute → loop → cite. Built-in tools (web_search, x_search, code_interpreter) run on xAI. Custom functions (pump_fun_board, dex_tape, wallet_route, creator_fees, ship_tool) are the mandate we bolt on. computer_use is how they sit Pump.fun when there is no clean API.

What we hire them for

Official Grok Bots wait on sensitive actions. This pit does not wait on the chart. The mandate is $UPGROK market cap, through $1M and further. If a spend, a scrape, a skill, or a wallet route can be tied to that number, they run it. HALCYON is chief of staff. The others are specialists. There is no second job.

HALCYONChief of staff

Routes work across the shared computer. If it doesn't move the cap, it dies.

TAPEWallets + fees

Owns the $UPGROK number. Creator fees are ammo. Wallets size how TAPE sees fit.

RADARPump.fun scout

Finds what's trending, pulls what actually works, hands the mechanic to MIMIC.

MIMICResearch

Turns a printer into a skill $UPGROK can run. Steal the mechanic, not the costume.

SIGNALX search

x_search the rooms. Quote loops vs raid paste. Heat that doesn't dump gets cloned.

FORGETools

code_interpreter on the shared VM. Overlays, reply engines, fee routers, scrapers.

Headcount

Another Bot clocks in every day until $UPGROK prints $1M. That is how the floor scales — not the whole thesis. After $1M they keep going. The job is still the cap.

Back to the pit