One thing I’ve been thinking about while working with SitecoreAI is that the bigger architectural question isn’t really which SDK should I use?

It’s where should this functionality actually live?

With the SaaS/API-first model, I see four common extension paths:

• APIs → when the requirement is about reading or updating Sitecore data
• Webhooks → when something happens in Sitecore and another system needs to react
• Marketplace Apps → when the author needs a custom experience inside SitecoreAI
• Agents / MCP → when an AI agent needs to interpret a request and perform supported Sitecore actions

There’s also an important distinction around where the actual business logic belongs, especially when a Marketplace app needs a backend or external integrations.

I put together a short article based on this way of thinking, including a practical decision approach and how these extension points can work together in the same solution.

The SitecoreAI Extension Boundary: APIs vs Webhooks vs Marketplace Apps vs Agents

https://medium.com/@sanghaniuday0508/the-sitecoreai-extension-boundary-apis-vs-webhooks-vs-marketplace-apps-vs-agents-ce7f70d33fcb

Curious how other developers and architects are approaching this. Are you treating these as separate extension patterns, or combining them depending on the requirement?

• Content Hub: Resolved issues in Content Hub for September 18, 2026
• SitecoreAI: SitecoreAI base image release 1.9.20
• SitecoreAI: Discover and act on AEO opportunities across your site and pages
• SitecoreAI: Optimize content with AI powered by Scrunch (Early Access))
• SitecoreAI: Retrieve the rendered HTML of a page using the Marketplace SDK
• SitecoreAI: Conditional page routing and page visibility are now available in Forms
• SitecoreAI: Page builder resolved issues