Instead of writing an agent from scratch, you assemble it from modular parts - datasets for knowledge, skillsets and abilities for actions, integrations for channels and APIs, a model of your choice, and a Blueprint that ties it all together. Each block is reusable across agents, so you build once and remix everywhere.

The main blocks are Datasets (knowledge and RAG), Skillsets and Abilities (tools and actions), Integrations (messaging channels and 150+ third-party providers), Blueprints (the visual design that composes an agent), Models (bring any provider), and Spaces and Widgets (where the agent is deployed). You mix and match them to build exactly the agent you need.

Yes. A dataset, skillset, or integration is defined once and can be attached to any number of agents. Update the block in one place and every agent that uses it picks up the change, so you avoid copy-and-paste drift.

No. The visual Blueprint designer lets you snap building blocks together without code. Developers who want full control can do the same thing through the SDKs and API, and both approaches operate on the same blocks.

Yes. Models, skillsets, abilities, and integrations are independent blocks, so you can switch from one provider to another or add a new tool without rewriting your agent logic. Reconfiguration is meant to be as fast as your product changes.

ChatBotKit supports multiple model providers including OpenAI, Anthropic, Mistral, and your own custom or self-hosted models. You pick the model that fits each agent and change it later without touching the rest of the composition.

Building directly on raw APIs means wiring up retrieval, tool calling, channel integrations, streaming, security, and observability yourself, then maintaining all of it. ChatBotKit provides those as managed, composable blocks on a single platform, so you assemble production agents instead of plumbing.

Yes. Every agent runs through configurable content moderation, PII filtering, policies, and access controls, with full observability and analytics built in. Security and governance wrap every block, so production behavior stays visible and controlled.