AI & Models · Integration
Chatbase
Add Chatbase to your product for your customers, and give your AI agents governed access to it.
Chatbase builds support agents trained on a customer's own documents and site content, and its API is served from the product domain at chatbase.co/api/v1 rather than an api subdomain, so requests to api.chatbase.co simply 404. Auth is a bearer token that is itself a JWT rather than an opaque key. The endpoint set is small and verb-shaped rather than RESTful, with paths like create-chatbot, update-chatbot-data, fetch-links, get-chatbots and get-conversations, so it does not map cleanly onto generated CRUD clients. Retraining is coarse: update-chatbot-data replaces the training material and the name, so an incremental source edit means resubmitting the corpus, and fetch-links crawls a supplied sourceURL to discover pages before ingestion. Conversations and captured leads are read back separately from the chat endpoint, which is where handover to a human usually hangs. fastn holds each customer's Chatbase key, maps their agent IDs to your tenants, and keeps the connection maintained as Chatbase reshapes its endpoints.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Chatbase account so your product can create and train a support agent on their help centre.
Retrain a customer's agent automatically whenever their documentation changes in your app.
Pull captured leads out of Chatbase conversations and into the customer's CRM record in your product.
Embed a customer's Chatbase agent in your own UI by calling the chat endpoint rather than using the hosted widget.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent retrain a customer's chatbot from an approved source list, with the chatbot ID, the sources submitted and the tenant recorded in a per-tenant audit log.
Have an agent review recent conversations and summarise the questions the bot failed to answer.
Let an agent list captured leads from a date range and flag those with no follow up recorded.
Example prompt
What questions did our Chatbase agent fail to answer last week, and which pages should we add to its training?
Set up Chatbase in 4 steps
- 01Enable the Chatbase connector from your fastn dashboard.
- 02Have each customer authorise their own Chatbase account, so calls run under their credentials rather than a shared key.
- 03Decide which models, requests and outputs your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Chatbase integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Chatbase integration without building it. Your customers connect their own Chatbase account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Chatbase update is not your on-call problem.
- One integration serves your product and your agents. The same governed Chatbase connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
Anthropic Claude
OpenAI
Azure OpenAIOften used alongside
Tools the same teams tend to run next to Chatbase, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeChatbase integration FAQ
How do I add a Chatbase integration to my product?
Enable the Chatbase connector in your fastn dashboard, then let each customer authenticate their own Chatbase account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Chatbase client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Chatbase account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Chatbase account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Chatbase integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent retrain a customer's chatbot from an approved source list, with the chatbot ID, the sources submitted and the tenant recorded in a per-tenant audit log.
Who maintains the Chatbase integration?
fastn does. When Chatbase changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose Chatbase API key and quota does each call use?
Each customer authorises their own Chatbase account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the Chatbase integration?
A common starting point: let a customer connect their own Chatbase account so your product can create and train a support agent on their help centre. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Chatbase integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Chatbase does not change your per-connector cost. You can start free with 3 connected accounts.
Add Chatbase to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.