What this is
AI agents go further than a userscript — they're autonomous, acting on a website on a user's behalf rather than just running a fixed script. They live in the botgentz_ai_agents table, which tracks things a simple userscript never needs: an ai_monthly_limit on usage, and an ai_system_prompt defining the agent's actual behavior and boundaries.
How it works
You define the system prompt that shapes what the agent does and how it behaves, and the platform handles the actual AI execution against that prompt, metered against the monthly limit tied to the agent's tier. This is the same underlying agent execution system that powers BotSurf's own voice-driven AI agents — you're building on the same infrastructure, not a separate, lesser one.
Holding BOT for this path
Agent developers are the clearest case for the BOT requirement: running an AI agent has a real, ongoing compute cost behind ai_monthly_limit, and holding BOT is expected to be how that capacity gets allocated to a developer's agents — not a one-time app-store fee, but an ongoing stake tied to how much agent capacity you're actually using.
Related paths in Apps & Agents