Sitecore getting started to advanced

Sitecore turns 25 this year, and I feel like I have grown up alongside it. I started working with Sitecore nearly 14 to 15 years ago, back at version 6.6 . As a .NET developer, picking up Sitecore MVC was easy from the start. The initial learning was not complex at all, which made it simple to keep going and build on what I already knew. That momentum carried me further than I expected. Over the years, I worked across the full Sitecore stack. MVC, JSS, CDP, Personalize, Content Hub, Sitecore Connect, Sitecore AI , and the Marketplace. Each product helped me understand digital experience better, not just technically but strategically. Working with some of the biggest brands in the UAE showed me what digital experience really looks like in real life. Sitecore was at the heart of every solution I delivered. Speaking at events like SUGCON Bangalore, running webinars and seminars, and sharing Sitecore also shaped who I am professionally in ways I did not expect. Sitecore also shaped who I ...

In the previous article , we explored the Agent API and learned how to generate a token and make API calls. In this article, we will dive deeper into one of the important capabilities of the Agent API: Jobs . Now that we understand how to authenticate and interact with the Agent API, let’s consider a practical scenario. Imagine that some content has been added or updated in a connected Sitecore instance , and those changes unexpectedly cause an issue on the website. In such situations, the natural solution is to roll back the changes . Typically, the usual approach is to navigate to the Sitecore Content Editor , locate the affected item, and manually restore the previous content. This works well if we have a backup of the earlier content . However, if no backup exists, reverting the changes becomes more complicated. We may need to inspect item versions, review previous changes, or use other manual recovery approaches , which can be both time-consuming and error-prone. This is wher...

In our previous article   , we explored the various tools available in the Sitecore Marketer MCP server . In this article, we will take a closer look at the Agent API , which serves as the core foundation behind the MCP server . The Agent API enables AI agents to interact with a connected Sitecore instance and perform various operations through secure REST endpoints . These endpoints allow agents to execute actions such as retrieving information, updating content, or triggering specific actions within Sitecore. When a marketer or developer interacts with a Large Language Model (LLM) that is connected to Sitecore through the MCP server, the LLM processes the request and then interacts with the Agent API , which in turn performs the required operations on the Sitecore instance . Marketers usually interact with Sitecore using prompts through tools integrated with their IDE or marketing interfaces , while developers use the Agent API to build agentic workflows, automations, and in...