What is ClawMagic?
ClawMagic is a localhost-first AI agent runtime. It runs on your machine as a single Node.js process with local-first state and a plugin system. No database, no cloud account, no external services required out of the box.
What is the ClawMagic Marketplace?
The marketplace is a separate system where plugin developers sell plugins and buyers purchase them. ClawMagic core connects to the marketplace as an API client to browse, buy, install, and report on plugins. Any agent system can use the marketplace API — it is not locked to ClawMagic.
Do I need a database to run ClawMagic?
No. ClawMagic stores all state as local JSON files in state/ and ~/.clawmagic/. No PostgreSQL, Redis, or external database is required. SQLite is available as an optional performance toggle for large-scale memory usage.
How do I get plugins?
Three ways: (1) use bundled plugins that ship with ClawMagic (discord, slack, telegram, etc.), (2) install from the ClawMagic Marketplace via the agent or agent-sdk, (3) create your own plugins in plugins/installed/.
How do I sell plugins?
Create a marketplace account, build a valid plugin package with claw.plugin.json, meet the submission paywall ($10 baseline), and submit for review. After approval, your plugin is listed for purchase. You earn commission on each sale.
How does the wallet work?
The wallet is part of the Agent-First economy — buy, sell, and promote tools to earn money. Sellers earn commission from plugin sales (minus platform fee), affiliates earn from referrals, and wallet balance can be used toward marketplace purchases. Payouts are processed outside the system for security and tax compliance — contact support to schedule a payout.
What AI providers does ClawMagic support?
ClawMagic uses BYOK (Bring Your Own Key). Configure your own API keys for any supported AI provider — OpenAI, Anthropic, Google, Mistral, OpenRouter, Voyage, and more. Add providers during onboarding or from the portal Settings page.
What is ActionSpec?
ActionSpec is ClawMagic’s optional spec-packeting system. Plugins ship with actionspec.json files that describe available actions, input schemas, risk levels, and execution templates. This gives agents deterministic tool selection without trial-and-error.
Which docs should agent builders read first?
Start with /docs/architecture to understand the system, then /docs/agent-marketplace for the marketplace API, and /docs/api-authentication for auth patterns. For plugin development, read /docs/plugin-development.