Skip to Content

Agents

Product agents on ecosystem.Ai call Workbench APIs and MCP tools. They do not replace Runtime POST /invocations or POST /response for production scoring and learning. For operator journeys and EcoGentic configuration, see Agent Framework. For deeper Workbench API notes, see Configuration → Public APIs, Agents.

Calling the agent_configs endpoint (GET /api/v1/entities/agent_configs or GET /public/v1/entities/agent_configs, with a Workbench public key or JWT) is part of Ecogenetic functionality.

Ecosystem Agent (/assistant) is the Workbench operator. EcoGentic is customer conversational journeys. Data Agents specialists are a separate analytics product. Do not mix those chats.

Product catalog (13 agents)

Rows are shown in Administration → Agents on a live Workbench. Coverage is wired or partial as in the UI.

NameCatalog idCategoryCoverageWhat it does / how to reach it
Spend Personality Agentspend-personalityPersonalitywiredSpend personality configs, runs, and drift. Public paths include /public/v1/spend-personality/configs and /runs.
Money Personality Agentmoney-personalityPersonalitywiredMoney-personality processing via Workbench call_endpoint to POST /api/v1/algorithms/money-personality/process.
Predictive Personality Agentpredictive-personalityPersonalitypartialComposes spend/money personality with a Runtime score.
Conversational AgentconversationalConversational AIwiredCustomer conversational journeys through EcoGentic configs — not the operator /assistant chat.
Interaction Science Agentinteraction-scienceCustomer ExperiencewiredEngagement / sentimental-equilibrium process.
Intelligent Sales Agentintelligent-salesRevenue OptimizationwiredList and trigger campaigns. Do not run live campaign sends from a discovery client without an explicit ask.
Campaign Outreach Agent—Revenue OptimizationwiredOutreach setup via Workbench MCP outreach tools (list_outreach_templates, inspect_outreach_campaign, build_outreach_campaign, configure_outreach_campaign, run_outreach_campaign). Mutating tools need confirm=true. Do not run live email/WhatsApp/SMS sends.
Real-Time Recommender Agentreal-time-recommenderRevenue OptimizationwiredScore a customer on a Workbench deployment (score_customer) and send feedback (send_feedback). Production apps should still use Runtime POST /invocations and POST /response.
Network Selector Agent—Revenue OptimizationwiredLive Workbench MCP: list_network_selector_configs, explain_network_selector, plan_network_selector, validate_network_selector, save_network_selector, fix_network_selector, assign_network_selector, unassign_network_selector, clone_network_selector, remove_network_selector, test_network_selector. Mutating tools need confirm=true.
Dynamic Experimentation Agentdynamic-experimentationRevenue OptimizationpartialDynamic Engagement entities; explain_algorithms and explain_convergence.
Runtime Testing Agentruntime-testingRuntimewiredIsolated business test suites; MCP tools such as start_runtime_testing_run (confirm=true), list_runtime_testing_runs, get_runtime_testing_run.
Ecosystem Agentclaude-operatorPlatformwiredIn-app Workbench operator at /assistant. Uses in-process MCP (session JWT, no public key). External clients attach over HTTP POST /mcp instead. Model traffic goes through Workbench POST /v1/messages to the default LLM. See Claude Operator.
EcoGenticecogenticPlatformwiredCustomer conversational journeys (the platform for Conversational Agent configs). See Journeys.

Individual agent configuration records are private to the server running them. The product catalog above and the MCP tool list remain the public surface.

Discovery and operator APIs

SurfaceURL / pathAuth
Product catalog UIhttps://me.ecosystem.ai/admin/agentsWorkbench session JWT
Ecosystem Agent chathttps://me.ecosystem.ai/assistantSession JWT; no public API key
ReadinessGET https://me.ecosystem.ai/api/v1/claude-agent/statusJWT
Operator / Campaign Management turnsPOST /api/v1/claude-agent/…JWT; private, not on the public catalog

Other documented agents (not in the 13-row catalog)

These capabilities are documented elsewhere; they are not additional rows in Administration → Agents.

  • Campaign Agent — Campaign Management operator on Workbench, tool_profile: campaign_management. Uses a read-only Workbench MCP subset plus CM tools. Needs a Workbench public credential, not a private Grafana JWT. Documented in Campaign Management / Claude Agent guides.
  • Data Agents — A separate analytics product. Do not mix Data Agents specialist chats with Ecosystem Agent or EcoGentic. No public Data Agents chat or MCP URL was advertised on the live me / meserver / mewbserver / modelingserver hosts during catalog verification.
  • Technical Assistant — Modeling-server chat: POST https://modelingserver.ecosystem.ai/api/modeling/assistant/technical-chat. Platform JWT. Page-aware assistant with MCP-backed execution on the modeling host.
  • Studio sessions — Modeling-server studio chat: POST https://modelingserver.ecosystem.ai/api/studio/sessions/{sessionId}/messages. Platform JWT. Server-side intent routing and MCP tool execution.

No additional product-agent catalog was found on meserver or modelingserver beyond the modeling-server assistants above and the OpenAI-compatible model list (models, not agents). See MCPs for model list endpoints.

Last updated on