An outreach agent that runs on its own timetable will keep spending whether or not anyone is watching, and a balance tells you where you are rather than where you will stop. Exposing the cap makes the ceiling explicit. Pause and resume as separate tools is the other necessary control — the correct response to an outreach programme going wrong is to stop it now, not to delete it. Be clear about what this does: resumed agents contact real people automatically, which is a category of automation to supervise deliberately rather than set and forget.
An outreach automation platform where agents run per channel against a product, with lead search, funnel reporting, activity logging and credit control around them.
- setup_business creates a product and its agents in one call from a business template, so the whole autopilot is configured rather than assembled.
- get_funnel reports conversion at each stage rather than a single response rate, which is where an outreach problem is actually located.
- Agents are controllable individually — run one immediately, pause it, resume it — and get_agent_stats reports connections and emails sent per agent.
- get_activity returns what agents actually did, which is the log you need when output looks wrong.
- get_credits reports balance, monthly spending cap and usage — a cap rather than only a balance.
- search_leads filters the lead database with pagination, and get_dashboard covers everything across products and agents.
SWARMIX_API_KEY. These agents send real outreach to real people, on a schedule, once resumed.
One command plus a key — npx -y swarmix-mcp, then supply credentials