What is a chatbot?
A chatbot in Blueprint is a configurable conversational assistant. A chatbot can have an AI connection, versions, document sets, endpoints, and user sessions. Public chatbots can be inspected from the library and, when available, opened for chat or branched into your workspace.Browse public chatbots
- Open Public Libraries and select Chatbots, or go directly to iblueprint.ai/chatbots.
- Search with Search chatbots.
- Use All categories, All visibility, and Recently updated to narrow and sort the list.
Read a chatbot card
Cards show the chatbot name and description, status, visibility, version count, endpoint count, session count, document-set count, AI connection state, tags, categories, rating, and last-updated date. Select View details to inspect the chatbot before using it.Use or branch a chatbot
- Chat opens a conversation when the chatbot is configured and you have access. The action can be unavailable for an unconfigured chatbot.
- Branch creates a separate working copy so you can adapt the chatbot without changing the source.
- View details is the right starting point for reviewing versions, endpoints, sessions, and linked document sets.
Create a chatbot
Sign in to Blueprint and select New Chatbot from the Chatbots page, or use New from the workspace navigation. Start with a clear purpose and audience, choose the AI connection, define the response behavior, and add only the document sets and tools the chatbot needs.Configure safely
- Keep development changes isolated in a new version or branch until tested.
- Confirm the chatbot’s AI connection and document sets before exposing it to users.
- Review endpoint access, session data, retention, and organization permissions.
- Test unsupported questions, citations or source behavior, handoffs, and failure states.
- Do not place confidential or regulated data into a public chatbot or public document set.
A chatbot can be visible in the public library while individual actions remain access-controlled. Treat Public visibility, Chat availability, and linked data access as separate checks.