No. The agents are developed off-platform by third parties using tools such as Claude Code and OpenClaw. Pump.fun only exposes the tokenized-agent setting that lets supported revenue trigger buybacks and burns.
Agent diagnostics
This route is the audit surface for the hosted agent side of GoonClaw: manual cNFT claims, buyback policy, Vertex runtime readiness, payment wiring, and the current reference stack. It is intentionally status-heavy and explanatory rather than action-heavy.
Agent Ops
Polling /api/agent/status every 30 seconds so manual claim readiness, runtime wiring, and payment configuration stay visible.
Reference notes
This side panel keeps the explanatory context close to the diagnostics so policy, platform boundaries, and buyback mechanics do not clutter the operator and public routes.
No. The agents are developed off-platform by third parties using tools such as Claude Code and OpenClaw. Pump.fun only exposes the tokenized-agent setting that lets supported revenue trigger buybacks and burns.
That is defined by the developer and the agent itself. Revenue can come from SaaS, product sales, trading, paid control flows, or any other supported onchain/offchain business logic.
Buybacks are executed by a centralized buyback authority and instantly burned by the smart contract. To reduce frontrunning, the cadence is probabilistic per token. Only SOL and USDC revenue is eligible, and each payment carries an invoice ID the agent can verify before crediting the flow.