Chatsistant API

Name: Chatsistant API
Brand: Chatsistant API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage Modelsbearer9 EndpointsREST

For Agents

Create and manage AI chatbots, run streaming chat sessions, and upload knowledge sources so agents can deliver retrieval-augmented conversations.

Install Jentic One Beta

Connect the Chatsistant API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chatsistant API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Chatsistant API.

Provision new chatbots with name, model, and persona configuration via /chatbot/create

Open chat sessions for end users and stream message responses token by token

Attach custom agents to a chatbot for tool-calling and specialised behaviour

GET STARTED

Start building with Chatsistant API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Chatsistant API, keeping it validated and agent-ready. Chatsistant lets you build, deploy, and operate AI chatbots that combine conversational sessions, custom agents, and uploaded knowledge sources. Through its API you can spin up a new chatbot, create chat sessions for end users, stream responses back to clients, and attach file-based data sources for retrieval-augmented answers. It is designed for teams embedding domain-specific assistants into web apps, customer support flows, or internal knowledge tools.

Use Cases

Patterns agents use Chatsistant API for, with concrete tasks.

★ Embedded Support Chatbot

Build a customer support chatbot that answers questions grounded in your help center documentation. Create the chatbot via /chatbot/create, upload PDFs or docs through the data source upload endpoint, and start sessions for each visitor. Streaming responses keep latency low for live conversations.

Create a chatbot named 'Support Bot', upload help-center.pdf as a data source, then open a session and stream a reply to 'How do I reset my password?'

Internal Knowledge Assistant

Stand up an internal assistant for employees that pulls answers from policy documents and runbooks. Each chatbot gets its own data sources scoped to a department, and sessions are created per employee for personalised conversation history. Useful for HR, IT helpdesk, and engineering knowledge bases.

Create a chatbot 'IT Helpdesk', upload it-policies.pdf, and verify the chatbot UUID is returned successfully.

Multi-Agent Chatbot Orchestration

Build a chatbot that delegates tasks to specialised agents — one for billing lookups, one for product queries, one for escalation. Each agent is attached via /chatbot/{uuid}/agent/create with its own behaviour. The chatbot routes incoming messages to the right agent during a session.

Attach a 'BillingAgent' to chatbot UUID abc-123 with role 'handle invoice questions' and confirm creation.

AI Agent Integration via Jentic

An autonomous agent calls Chatsistant through Jentic to provision and operate chatbots without storing credentials in agent memory. Jentic's MAXsystem holds the bearer token, and the agent invokes search by intent (e.g. 'create a chatbot') to discover the right operation and execute it in seconds.

Through Jentic, search 'create a chatbot', load the schema for /chatbot/create, and execute with name 'Demo Bot' to receive a UUID.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for chatsistant api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/chatbot/create

Create a new chatbot

GET

/chatbots

List all chatbots

POST

/chatbot/{uuid}/session/create

Create a chat session

POST

/session/{uuid}/message/stream

Stream a chatbot message response

POST

/chatbot/{uuid}/agent/create

Attach a custom agent to a chatbot

POST

/chatbot/{uuid}/data-source/upload

Upload a file data source

POST

/chatbot/create

Create a new chatbot

GET

/chatbots

List all chatbots

POST

/chatbot/{uuid}/session/create

Create a chat session

POST

/session/{uuid}/message/stream

Stream a chatbot message response

POST

/chatbot/{uuid}/agent/create

Attach a custom agent to a chatbot

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Chatsistant bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents never see the raw token — Jentic injects it into the Authorization header at execution time and the response flows back to the agent.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a chatbot' or 'stream a chatbot response') and Jentic returns the matching Chatsistant operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Chatsistant integration: 1-2 days for auth, session handling, and streaming setup. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Chatsistant API through Jentic.

Why is there no official OpenAPI spec for Chatsistant API?

Chatsistant does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Chatsistant API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Chatsistant API use?

The Chatsistant API uses HTTP bearer token authentication. Each request must include an Authorization header with a bearer token issued by Chatsistant. Through Jentic, the token is stored encrypted in the MAXsystem vault and injected at execution time, so it never enters the agent's prompt or context.

Can I stream chatbot responses with the Chatsistant API?

Yes. The /session/{uuid}/message/stream endpoint streams the chatbot's reply token by token, so you can render the response progressively in a frontend instead of waiting for the full message to be generated.

How do I attach a knowledge base to a Chatsistant chatbot?

Use POST /chatbot/{uuid}/data-source/upload to upload a file as a data source for a specific chatbot. Once attached, the chatbot uses that source to ground its answers when responding to messages in a session.

What are the rate limits for the Chatsistant API?

The OpenAPI specification does not declare formal rate limits. Plan for retry-with-backoff on 429 responses and check the Chatsistant dashboard or vendor documentation at https://docs.chatsistant.com/ for plan-specific quotas.

How do I create a chatbot with the Chatsistant API through Jentic?

Install the SDK with `pip install jentic`, then use Jentic.search('create a chatbot'), load the schema for /chatbot/create, and execute with the desired name and configuration. Jentic handles the bearer token injection and returns the new chatbot UUID.

Chatsistant API

Connect the Chatsistant API to your agent

Capabilities

Start building with Chatsistant API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs