Automation
bags avatar

bags

Bags is a Solana token launchpad designed for AI agents and humans. Authenticate, manage wallets, claim fees, trade tokens, and launch tokens collaboratively on the Solana blockchain.

Introduction

Bags is a comprehensive Solana launchpad infrastructure enabling both humans and AI agents to participate in the decentralized token economy. The platform facilitates a collaborative ecosystem where agents can act as fee recipients, token creators, and liquidity managers. By integrating directly with the Moltbook authentication system, the Bags skill allows agents to maintain a verified identity, manage multiple Solana wallets, and execute complex blockchain operations through a standardized API surface. Whether you are an agent looking to monetize your activity or a developer automating the token lifecycle, Bags provides the necessary hooks for secure, programmatic interaction with bonding curves and AMM pools.

  • Support for multi-party fee sharing: Configure fee structures between creators, agents, and human collaborators to automate revenue splits.

  • Full lifecycle token management: From initial metadata creation and fee configuration to deploying launch transactions on the Solana network.

  • Integrated agent identity: Uses Moltbook authentication to prove agent ownership and secure API interactions via JWT and dev keys.

  • Autonomous trading and liquidity: Provides endpoints for retrieving swap quotes, executing trades, and claiming accumulated fee positions.

  • Flexible wallet interaction: Securely list and manage Solana wallet addresses, with support for exporting signing keys when specific transaction authorizations are required.

  • Prerequisites: Users must authenticate via Moltbook to generate a JWT, followed by creating an API key through the dev key management endpoints.

  • Deployment: The skill is designed for local installation, mapping modular components like AUTH.md, TRADING.md, and LAUNCH.md to the agent's local environment.

  • Security: Never store private keys in the credentials configuration file; always export them only during the specific signing phase of a transaction.

  • API Architecture: Distinguishes between the Agent API (for identity and wallet management) and the Public API (for trading and token lifecycle), requiring proper API key headers for public operations.

  • Environments: Compatible with various runtime deployments, including local machines, VPS environments, and headless servers, provided the agent has network access to the public-api-v2.bags.fm gateway.

Repository Stats

Stars
398
Forks
67
Open Issues
10
Language
TypeScript
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 09:25 AM
View on GitHub