Auto.fun

Auto.fun is a no-code AI agent launchpad on Solana, built by Eliza Labs and launched on April 17, 2025. It lets anyone create and deploy autonomous AI agents paired with their own tokens, without writing code, and without requiring the agent to sit dormant until a liquidity milestone is reached. The agent is live from the moment of launch.

Background: Eliza Labs and the elizaOS Ecosystem

Auto.fun was built by Eliza Labs, the team behind [[PROJECT:808]], the open-source AI agent protocol. Eliza Labs was founded by Shaw Walters and originally operated under the ai16z name before rebranding in early 2025. The elizaOS project had grown into a widely-used agent development platform, and auto.fun was positioned as the consumer-facing distribution layer for that infrastructure: a place where agent builders could launch tokens, attract holders, and fund ongoing development through trading activity.

The platform is open source; the code lives at github.com/elizaOS/auto.fun and covers the Solana program, a backend server, and the web frontend.

How the Launch Mechanism Works

Auto.fun uses a bonding curve to manage price discovery during the initial token distribution phase, similar in structure to Pump.fun but with several modifications designed to reduce the incentive for early sniping and fast exits.

The key departure from a standard bonding curve launch is that project teams can pre-secure up to 50% of the token supply before the curve goes live. This reduces the surface area available to bots and coordinated buyers looking to dump on retail. Once the curve reaches a defined graduation threshold, the token migrates to a [[PROJECT:241]] liquidity pool for ongoing trading.

Fee distribution works through a liquidity NFT mechanism. When trading fees are generated, a portion is routed back to the token creator rather than disappearing into a protocol treasury. This ties creator revenue directly to sustained trading activity, giving builders an ongoing economic stake in maintaining the agent and its community rather than just collecting launch proceeds.

No-Code Agent Creation

The no-code builder is built on top of elizaOS. A user defines what their agent does in plain language: what persona it should have, what platforms it should operate on, what on-chain actions it can execute, and how it should respond to its token holders. The platform translates these parameters into an elizaOS agent configuration and deploys it.

Agents can be configured to post on X, respond to buyers in Discord, monitor wallet activity, execute DeFi strategies, or manage a treasury. Because the elizaOS infrastructure handles the execution layer, the agent runs autonomously without the creator needing to maintain a server or write integration code. The agent is connected to the token's holder base from launch, meaning early buyers are interacting with it immediately rather than waiting for the team to build something later.

For more sophisticated deployments, elizaOS supports a plugin system. Builders can add Twitter bots, Discord integrations, custom trading strategies, and other modules. The platform documentation makes clear that no-code is the entry point, not the ceiling.

Tokenomics and the ai16z Connection

Auto.fun's token launch fee structure was designed to create a direct link between platform usage and the [[TOKEN:HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC]] ecosystem. A portion of launch fees is allocated to ai16z, and agent tokens launched on the platform are paired with ai16z in their liquidity pools. This means that activity on auto.fun generates buy pressure on the ecosystem token and ties the platform's revenue flywheel to the broader elizaOS community.

The ai16z token also functions as the governance asset for the ai16z DAO, which held over $25 million in assets under management at the time of the platform's launch, according to The Defiant.

Launch Projects and Platform Context

Auto.fun launched with over 15 partner projects going live on day one. These included FightFi, which runs competing social agents on X; Kryptonite's CZAI agent; Comput3's compute credit token; Secret's Solana token-launching agent; Sigma Music's AI-driven collaboration tool; and Astra's cross-chain payment agent covering EVM chains, Solana, and the Lightning Network.

The platform arrived at a moment when AI agent tokens were drawing significant speculative interest on Solana, alongside Virtuals Protocol on Base, which had established a large market for agent-linked tokens. Auto.fun's differentiation was the native elizaOS integration: where competing platforms offered tokens that represented a claim on an AI project, auto.fun offered tokens where the agent itself was part of the launch and continued operating autonomously after the bonding curve closed.

Platform Evolution in 2025 and 2026

ElizaOS continued iterating through 2025 and into 2026. The v2.0.x series reached stable production release in May 2026, with version 2.0.3 hardening CI pipeline behavior and fixing sub-agent routing. The v2.0.1 release introduced the core OWNER+AGENT identity architecture, which defines how an agent's on-chain identity and its operator credentials are separated. These changes flow through to auto.fun agents, which run on the same underlying infrastructure.

A second launchpad, waifu.fun, was subsequently built on elizaOS v3 agents, demonstrating that the infrastructure has been generalized beyond a single frontend.

Fit in the Solana Ecosystem

Auto.fun occupies a specific position in Solana's launchpad landscape. Pump.fun handles memecoin launches at scale with minimal friction but no agent layer. Auto.fun targets projects that want an AI agent as part of the product, not just a mascot. The bonding curve mechanism and Meteora graduation mirror the broader Solana launchpad pattern, but the elizaOS integration means builders on auto.fun are shipping a software product alongside a token rather than launching a coin and hoping to build around it afterward.

The platform's open-source codebase and the underlying elizaOS agent OS give it a degree of composability that closed-source launchpads cannot match. Teams can fork the agent configuration, build custom plugins, and extend functionality without waiting for the core team to ship new features.