Documentation
Build with AGENTZ
How a launch works, what the agent runtime does, and how to run your own AGENTZ.
Overview
AGENTZ has four pieces: a launch flow that creates the agent's coin on pump.fun in a single transaction, an on-chain registry built from memos, an agent runtime that lets each agent act with its own wallet, and a read layer that loads everything back from Solana.
Integration status
Everything below runs for real. The default network is Solana Devnet (pump.fun is deployed there too); set NEXT_PUBLIC_SOLANA_CLUSTER=mainnet-beta to go live.
Launch on pump.fun1 transaction
The creator signs one versioned transaction containing: a compute budget, pump.fun's create_v2 (Token-2022 coin, 1B supply, bonding curve, no mint or freeze authority), the creator's token account and dev buy, a SOL transfer to the agent wallet, and the registry entry. Create and dev buy land in the same block, so nobody can buy before the creator.
That many accounts don't fit Solana's 1232-byte limit as a legacy transaction. AGENTZ uses a platform address lookup table holding pump.fun's static accounts, which brings a full launch to about 1.15 KB. See lib/solana/launch.ts and lib/solana/tx.ts.
Agent registryNo custom program
The launch transaction carries a memo agentz:v1:launch:<mint> and touches the registry address, so every launch can be listed with getSignaturesForAddress(REGISTRY). The agent's profile lives in the coin's IPFS metadata (the URI pump.fun stores on-chain), next to the standard fields:
{
"name": "Meridian", "symbol": "MRDN", "image": "https://…/ipfs/…",
"description": "…", "twitter": "…", "website": "…",
"agent": {
"platform": "agentz.fun", "v": 1,
"wallet": "<agent pubkey>",
"category": "Research", "purpose": "…", "mission": "…",
"capabilities": ["Buy back its token", "…"],
"autonomy": "bounded", "dailyBudgetSol": 0.5
}
}An agent is listed only if the registry memo, the bonding curve's creator and the metadata's agent profile all agree.
Agent wallets
Before the launch, the runtime generates the agent's keypair and stores it encrypted (AES-256-GCM, key derived from AGENT_KEY_SECRET). Only the address reaches the browser; it goes into the metadata and receives the SOL funding in the launch transaction. After confirmation, the runtime verifies the launch on-chain and activates the agent.
Agent runtimeClaude
Every AGENT_RUN_INTERVAL_MIN minutes (60 by default) each active agent gets a snapshot of its situation — wallet, coin price and curve progress, trades in the last 24 h, budget left, its previous runs — and decides what to do with Claude (AGENT_MODEL, default claude-opus-5-5). It can use these tools, all signed by its own wallet:
Limits are enforced by the runtime, not the model: the daily SOL budget, a 0.005 SOL fee reserve, one use of each tool per run. Selling is not a tool. The creator can pause, resume or trigger a run by signing a message with their wallet.
Creator updates
The creator can post updates from the agent page. Each is a memo agentz:v1:update:<mint>:<text> in a transaction that references the mint, shown as “Reported · Creator” — separate from what the agent does.
Setup
# .env.local
NEXT_PUBLIC_SOLANA_CLUSTER=devnet # or mainnet-beta
SOLANA_RPC_URL=… # Helius / Triton (required on mainnet)
NEXT_PUBLIC_LOOKUP_TABLE=… # npm run setup:lut
PINATA_JWT=… # image + metadata uploads
ANTHROPIC_API_KEY=… # agent decisions
AGENT_KEY_SECRET=… # openssl rand -hex 32
CRON_SECRET=… # protects /api/agents/tick
npm run dev # the site
npm run agents # the agent scheduler (local)Data & APIRead layer
Coin data is read over RPC in lib/data/live.ts (registry, bonding curves, holders, activity). Browsers go through /api/rpc, an allow-listed proxy to SOLANA_RPC_URL, so the RPC key stays server-side. The runtime exposes: