Install Jentic One Beta

Connect the Botsonic-Api-Docs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Botsonic-Api-Docs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbotsonic.ai%2Fbotsonic" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbotsonic.ai%2Fbotsonic" | 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 Botsonic-Api-Docs API.

Generate a chatbot response, synchronously or streamed, for a user message

Create and configure bots and retrieve their details

Train a bot by uploading files, raw text, or bulk URLs

Manage a bot's FAQs and starter questions

Read a bot's conversations, including the source behind each answer

GET STARTED

Start building with Botsonic-Api-Docs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Botsonic-Api-Docs API for, with concrete tasks.

★ Agent-served support bot

An AI agent answers customer questions through a Botsonic bot. Through Jentic the agent sends a user message to the response operation and reads back the answer, synchronously for a single reply or streamed for a typing effect. Because each bot is trained on the company's own content, the answers stay grounded in that material.

Send a user question to a bot's response operation and return the generated answer

Content-trained bots

A team grounds a bot in its own documentation. The bot-data operations ingest training content as an uploaded file, raw text, or a bulk list of URLs, so an agent can build or refresh a bot's knowledge from a help center or a set of documents. The bot then answers from that content rather than generic knowledge.

Bulk-upload a list of help-center URLs to a bot, then generate a response to confirm it answers from them

Conversation review

A team audits what its bot is telling customers. The conversation operations return a bot's conversations, including the source behind each answer, so an agent can review transcripts, spot gaps, and decide what new training content to add. This closes the loop between serving answers and improving them.

List a bot's recent conversations with their answer sources and summarize the questions it could not answer well

Key Endpoints

24 endpoints — the botsonic api builds and serves ai chatbots trained on your own content.

METHOD

PATH

DESCRIPTION

POST

/v1/business/botsonic

Generate Sync Or Streaming Response

POST

/v1/business/bot

Create Bot

GET

/v1/business/bot/all

Get All Bots

POST

/v1/business/bot-data/upload-file

Upload File

POST

/v1/business/bot-data/bulk-upsert-urls

Bulk Upload Urls

GET

/v1/business/bot-data/conversations/all

Get All Conversations

POST

/v1/business/bot-faq

Create Single Faq

POST

/v1/business/bot-starter-questions

Create Starter Question

POST

/v1/business/botsonic

Generate Sync Or Streaming Response

POST

/v1/business/bot

Create Bot

GET

/v1/business/bot/all

Get All Bots

POST

/v1/business/bot-data/upload-file

Upload File

POST

/v1/business/bot-data/bulk-upsert-urls

Bulk Upload Urls

GET

/v1/business/bot-data/conversations/all

Get All Conversations

POST

/v1/business/bot-faq

Create Single Faq

POST

/v1/business/bot-starter-questions

Create Starter Question

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Botsonic API by hand means handling three API-key headers (a bot key in X-BOT-KEY, a user key in USER-API-KEY, and a bot token in the token header), choosing the right one per operation, and managing training-data uploads yourself. Through Jentic you install once, import it from the API Directory, store the keys once, and your agent calls it.

Permission scoping

The Botsonic API puts the bot id in the URL path (/v1/business/bot/{bot_id}), so a rule can pin your agent to one bot: it can generate responses and read that bot's conversations without reaching bot deletion or other bots. You choose the operations it may call, so deleting a bot or its data is not included unless you add it.

Credential isolation

Your Botsonic keys are held once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a chatbot response' or 'train a bot on documents', and Jentic returns the matching Botsonic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Botsonic-Api-Docs API through Jentic.

What authentication does the Botsonic API use?

The Botsonic API authenticates with API keys sent in request headers per its OpenAPI spec: a bot key in the X-BOT-KEY header, a user key in the USER-API-KEY header, and a bot token in the token header, each used by different operations and requiring business access. Through Jentic the keys are injected at call time by your own Jentic One instance, so they never enter the agent's prompt or logs.

Can I train a Botsonic bot on my own content?

Yes. The bot-data operations ingest training content three ways: upload a file, upload raw text, or bulk-upload a list of URLs. Once the content is added, the bot's responses draw on it when it answers a user.

What are the rate limits for the Botsonic API?

The OpenAPI spec does not specify rate limits, and several operations require business access. Check the Botsonic documentation at https://botsonic.ai for current limits and plan requirements.

Is there a Botsonic MCP server?

You don't need an MCP server to give your agent the Botsonic API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent calls it, so you skip installing and syncing a separate server.

Can I limit what my agent is allowed to do with the Botsonic API?

Yes. Write a rule that allows only the response-generation and conversation-read operations for one bot, so your agent can answer and review conversations but cannot delete the bot or its training data. Every call it makes is logged.

How do I generate a chatbot response with the Botsonic API through Jentic?

Search Jentic for 'generate a chatbot response' and it returns the response operation with its input schema; the agent passes the bot key and the user message and reads back the answer, synchronously or streamed. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Botsonic-Api-Docs

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsChat MessagingapiKey24 EndpointsREST

For Agents

Build and run AI chatbots: create bots, train them on files, text, or URLs, generate sync or streaming responses, manage FAQs and starter questions, and read conversations.

Use for: Generate a chatbot response for a user question, Create a new bot in Botsonic, Train a bot by uploading a document, Add an FAQ to a bot

Not supported: Does not send email or SMS, host a live-agent helpdesk, or run voice calls. Use for building and serving AI chatbots only.

The Botsonic API builds and serves AI chatbots trained on your own content. An agent creates and configures bots, trains them by uploading files, raw text, or bulk URLs, and generates chatbot responses either synchronously or as a stream. It manages each bot's FAQs and starter questions, reads conversations along with the source behind each answer, and retrieves a bot's API token for embedding. Several operations require business access.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Botsonic-Api-Docs to your agent

Capabilities

Start building with Botsonic-Api-Docs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Botsonic-Api-Docs

Jentic AI Readiness Score

Botsonic-Api-Docs

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness