ChatBotKit

Install corsair and @corsair-dev/chatbotkit, add the ChatBotKit plugin, and connect with an API key. Then call methods like corsair.chatbotkit.api.blueprints.create() from your app. Corsair syncs data per tenant.

Yes. ChatBotKit requires an API key from your ChatBotKit account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit ChatBotKit, GitHub, Notion, Stripe, and the rest. Trigger ChatBotKit from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for ai chatbot platform for building conversational agents with custom knowledge bases. Common builds include sync jobs, admin tooling, and agents that call ChatBotKit APIs from your backend. Local DB entities let you query synced ChatBotKit records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per ChatBotKit API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/chatbotkit in the open repo. When ChatBotKit ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your ChatBotKit data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ChatBotKit data on your behalf.