Aiko Agent

Accelerate time-to-impact with Aiko

Aiko helps you get real work done in Kontent.ai. Unlike AI chatbots that stop at suggestions, Aiko breaks down your tasks into steps, navigates your content model, executes changes, and shows you the results. Whether you need to audit existing content, perform bulk operations, or create new content at scale, Aiko handles the complex tasks while you focus on strategy and outcomes. With Aiko, you can, for example:

• Find outdated content items and create a plan for improving SEO and GEO
• Review and edit a content item and apply the same changes to all existing language variants
• Draft content items based on your inputs
• Translate and publish items across multiple languages

Watch the video below to learn what Aiko can do.

Get access to Aiko

In new projects, Aiko Agent is active by default. To give users access to Aiko, you also need to add the Access Aiko Agent permission to their roles. If Aiko isn't active in your project, a project manager needs to first activate Aiko.

1. In Environment settings, go to AI features.
2. Click Activate Aiko Agent.

Add the permission to a role

Any user with the Manage custom roles permission can add the permission to access Aiko to roles.

1. In Environment settings, go to Roles.
2. Click the role you want to give access to Aiko Agent.
3. Select the Access Aiko Agent permission.
4. Click Save changes.

Users with this role see Aiko Agent in the navigation and the button in the top right on every page in your environment. If you still don't see Aiko, contact our Support team.

Ask Aiko from any page

You can open Aiko from any page in your environment, so you can get help right where you work, without going to Aiko Agent in the main navigation.

1. Go to any page in your environment.
2. In the top right, click .

Aiko opens in a panel on top of the page. The button isn’t available in the project list, in project settings (general settings, Environments, and API keys), in subscriptions, or in your user profile.

What Aiko can see

Aiko works across your project from any page. When you refer to something on your screen, such as “this item” or “the selected items”, Aiko checks which page you're on and, in some places, what you're working on there:

• Content item editor: the item you’re editing and its language
• Content item inventory: which types of filters you applied, your search phrase, and your item selection
• Asset library: which types of filters you applied, your search phrase, your asset selection, and the asset you have open
• Content model: your selection in the list of content types, snippets, and taxonomy groups, and whatever you have currently open

How to use Aiko

As you chat with Aiko, here are some example prompts you can customize to match your needs.

Audit, find, and update content

• “Find all mentions of our old product name ‘A’ across content items, assets, and URL slugs. Update them to our new product name ‘B’ while preserving URL redirects. Create a report showing all changed items.”

Explore what’s in your content

• “List all content types in my project grouped by their usage count. Show me which types have content items and which are empty.”

Model, create, and research content

• “Design a content type called Product Review with these elements: Rating (number 1-5), Pros (rich text, required), Cons (rich text, required), Summary (text, 160 characters max, required), Reviewer Name (text, required), Review Date (date & time, required), and Product Category (multiple choice taxonomy).”
• “Research the latest trends in sustainable fashion from the past 3 months. Create a blog post that explains each trend with specific brand examples and end with how our products align with these trends.”

Perform bulk operations

• “Schedule all articles by John Roy that are in the Review workflow step to publish on September 30 at 9:00 a.m. UTC.”

Find more examples and learn best practices for crafting effective prompts.

Review Aiko’s changes

After Aiko performs bulk updates to your content items, you can verify the intended changes directly in the chat. You’ll see an expandable bar showing the content item’s name. Expand to view only the elements that were modified with highlighted changes. These changes are also found in the item’s version history. This focused view helps you quickly assess Aiko’s work before publishing.

Manage your chat history

Your conversations with Aiko are preserved and accessible across your devices in Aiko Agent > Chats.  You can also open your chats by clicking the button in the top right corner anywhere in your environment. Click Chats to pick an earlier chat, or click New chat to start a fresh one. You see the same chats as in Aiko Agent > Chats. To remove chats you no longer need:

1. Click next to the chat.
2. Select Delete.

If Aiko is actively responding or has a bulk operation in progress, wait for it to complete or stop the operation before deleting the chat.

Monitor bulk operations

Aiko handles bulk operations in one of two ways:

• Sequential: Results appear step by step directly in the chat. To stop the operation, click next to the chat message.
• Background: Operations that are delegated to run in the background and continue even if you close the browser or sign out. Once processing starts, click next to the operation in the chat to see what’s been updated and what’s still pending. When the background bulk operation is complete, the results appear in the chat.

In Aiko Agent in the main navigation, you can also monitor background operations from the chat list, where affected conversations show a status icon indicating whether an operation is still running, completed with results ready to review, or failed. If multiple states apply, the error state takes priority. When you use Aiko from any other page, the button shows when Aiko is working and when a new response is ready.

Stop bulk operations

To stop a background bulk operation:

1. Go to Aiko Agent > Chats.
2. Select the chat with the running bulk operation.
3. Click next to the running operation in the chat.
4. Click Stop task.

Considerations

When working with Aiko, keep the following points in mind.

Accuracy and scope

• Aiko can make mistakes. Always review the changes made to your content.
• Aiko works within your existing content model and can only make changes as instructed.
• Aiko respects your established workflow steps, roles, and permissions, accessing only what you’re allowed in the project.
• While Aiko understands conversational requests, being specific and using Kontent.ai terminology in your request yields better results.

Conversations and operations

• Via button, Aiko can respond in several chats at once, so you don't have to wait for one chat to finish before you start another. On the Aiko Agent page, Aiko responds in one chat at a time. Bulk operations can continue running in the background across multiple conversations.
• Large-scale changes are processed systematically. Aiko informs you of its progress and any issues encountered during bulk operations.
• Aiko delegates background bulk operations to expert agents, which always use the Balanced option of the Task complexity setting.
• Text you typed but didn't send is lost when you close Aiko.
• Older chats will be automatically removed after a period of inactivity.

Working with Aiko from any page

• If you leave the environment while Aiko is working, you're asked to confirm. If you leave anyway, Aiko stops and doesn’t finish the task. Changes it already made are kept, and the chat may not show Aiko's last response. Background operations keep running.
• On pages with a Save button, save your changes before you ask Aiko to change something on that page. Aiko can’t see unsaved changes, and saving afterward could overwrite what Aiko changed or fail with a conflict.
• Aiko doesn't see your screen. When you refer to something on the page, Aiko checks which page you're on and, in some places, what you're working on there. It reads the content itself through its usual tools.
• In content item inventory, Aiko acts on the items you selected, not on everything your filters show. If you use Select all, Aiko can act on the selection only after every item in the list has loaded.

Resources and data

• Aiko uses your subscription’s allocated API calls and bandwidth to perform operations.
  • Most requests consume multiple API calls and bandwidth, while bulk operations require resources proportional to the number of items processed.
  • Bulk operations continue consuming API calls, bandwidth, and AI credits until they finish or are canceled, even when running in the background.
• Aiko doesn’t use your data for training. Your content remains secure and private.

Languages

• Aiko cannot activate or deactivate languages. New languages are always created as active. To change a language’s status, use the Kontent.ai UI.
• When working with multilingual content, specify the target languages clearly.

Content tracking

• Changes made by Aiko are labeled with the user’s name followed by “via ✨ Aiko” in both version history and the audit log, so you can tell them apart from changes made directly by a user.
• Aiko relies on the Management API, which does not support comments and suggestions, so any comments in elements that Aiko edits are resolved. This is a known limitation to consider when comments are used in content items that may be modified by Aiko.

Help shape what comes next

Your input helps us improve this capability. If you have any suggestions, questions, or feedback, we’d love to hear from you. Share your experience using the button in Kontent.ai or in the Learn portal.