Solana agent ecosystem map surfaces stacks

A new Solana agent map is getting attention because it turns a messy pile of tools into a stack you can actually read: agent frameworks at the base, wallets and payment rails in the middle, and launchpads and social distribution at the top. The names on it are not random projects; they are the parts an autonomous crypto app needs if it is going to trade, post, pay, and launch without a human clicking every button. (x.com) (docs.elizaos.ai) (docs.openclaw.ai) The easiest way to think about an “agent stack” is a food-delivery app for software. One layer decides what to do, one layer holds the money, one layer talks to blockchains and social apps, and one layer turns the whole thing into a token or product people can discover. (elizaos.ai) (docs.cdp.coinbase.com) (docs.openclaw.ai) On the framework side, elizaOS is one of the clearest building blocks because its official documentation says agents can plug into Discord, Telegram, X, Hypertext Transfer Protocol endpoints, and Solana from one event pipeline. Its Solana plugin adds wallet management, token transfers, swaps, and portfolio tracking, which is the difference between a chatbot that talks and an agent that can actually move money. (elizaos.ai) (docs.elizaos.ai 1) (docs.elizaos.ai 2) OpenClaw sits closer to the “do things for me” end of the market. Its docs describe it as a self-hosted gateway that connects chat apps like WhatsApp, Telegram, Slack, and Discord to always-on agents, and its Solana quickstart shows those agents being funded with Solana’s SOL token and the USDC stablecoin so they can trade autonomously. (docs.openclaw.ai) (github.com 1) (github.com 2) The payment rail in the middle is x402, which is built around the old Hypertext Transfer Protocol status code “402 Payment Required.” The x402 docs say it lets software pay for an application programming interface call or a piece of content directly over the web, with support for Base, Polygon, and Solana through Coinbase’s facilitator and broader multi-network support in the open standard docs. (docs.x402.org) (docs.cdp.coinbase.com) (docs.x402.org) That matters because agents do not just need wallets; they need a way to buy services one request at a time. If an agent wants to pay for market data, an image model, or a trading signal without opening an account and storing an application programming interface key, x402 is one of the cleaner ways to do it. (docs.x402.org) (docs.cdp.coinbase.com) (docs.x402.org) The cross-chain wrinkle is that x402 activity has been heavily associated with Base so far because Coinbase’s own x402 materials center Base as a supported network and use its network identifier in examples. The Solana angle is not that Solana invented this payment rail; it is that Solana builders can bolt the same payment behavior onto faster, cheaper consumer apps and pull that activity into a different chain environment. (docs.cdp.coinbase.com 1) (docs.cdp.coinbase.com 2) (docs.x402.org) Then you get to launchpads, where the token narrative starts. One public AgentPad codebase describes itself as “the launchpad for tokenized AI agents on Solana,” built on pump.fun, with one-click agent initialization, automatic buybacks, and a generated Skills.md file for payment integration. (github.com) (github.com) That is the part speculators care about, because launchpads turn infrastructure into coins people can trade. If frameworks like elizaOS and OpenClaw are the engine and x402 is the toll booth, launchpads like AgentPad are the storefront that packages the whole machine into a ticker, a mint address, and a meme. (github.com) (github.com) (openclaw.ai) Solana already had the ingredients for this before the infographic landed. The open-source Solana Agent Kit has more than 1,700 GitHub stars and describes itself as a toolkit for connecting artificial intelligence agents to Solana protocols, which means there was already developer plumbing waiting for a cleaner market map. (github.com) So the map is useful for a simple reason: it separates “agent” into categories people had been mixing together. elizaOS is a framework, OpenClaw is an execution and channel layer, x402 is a payment standard, and AgentPad is a launch surface; once you sort those roles, it becomes easier to see where the next Solana token wave could form. (docs.elizaos.ai) (docs.openclaw.ai) (docs.x402.org) (github.com)