For Agents
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendBird Chat Platform 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 | shStep 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 instanceJentic 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.
What an agent can do with SendBird Chat Platform API.
scheduleAnAnnouncement
createABot
listBots
viewBotById
GET STARTED
Create SendBird chat users and channels, send and edit the messages inside them, run bots, moderate members, and schedule announcements. 92 operations, authenticated with an `Api-Token` header.
Use for: I need to schedule an announcement to my chat channels, I want to create a chat bot on my SendBird application, List the bots registered on my SendBird application, Look up a bot by its user id
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
The SendBird Chat Platform API creates chat users and their session tokens, opens group and open channels, and sends, edits and lists the messages inside them. It also registers bots that post into channels, schedules announcements, appoints channel operators, freezes channels and blocks users, stores channel and user metadata, and reports daily and monthly active user counts. Every call carries an `Api-Token` header and is addressed to the host belonging to one SendBird application.
updateBotById
deleteBotById
joinChannels
Patterns agents use SendBird Chat Platform API for, with concrete tasks.
★ Communications Operations
Run chat operations from your backend instead of the SendBird dashboard: create users and issue their session tokens, open group and open channels, send and edit the messages inside them, and schedule announcements.
Call POST /v3/announcements to schedule an announcement
Automated Bot Management
Chain several SendBird Chat Platform API endpoints in one workflow: create a bot, list the bots registered on the application, add the bot to a set of group channels, and update its nickname or profile later.
Call POST /v3/bots to create a bot, then POST /v3/bots/{bot_userid}/channels to add it to group channels
AI Agent Integration via Jentic
AI agents discover and call SendBird Chat Platform API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read the API reference or handle the `Api-Token` header manually.
Search Jentic for 'schedule an announcement', load the operation schema, and execute with Jentic-managed credentials
92 endpoints — the sendbird chat platform api creates chat users and their session tokens, opens group and open channels, and sends, edits and lists the messages inside them.
METHOD
PATH
DESCRIPTION
/v3/announcements
scheduleAnAnnouncement
/v3/bots
createABot
/v3/bots
listBots
/v3/bots/{bot_userid}
viewBotById
/v3/bots/{bot_userid}
updateBotById
/v3/bots/{bot_userid}
deleteBotById
/v3/bots/{bot_userid}/channels
joinChannels
/v3/bots/{bot_userid}/channels
botLeaveGroupChannels
/v3/announcements
scheduleAnAnnouncement
/v3/bots
createABot
/v3/bots
listBots
/v3/bots/{bot_userid}
viewBotById
/v3/bots/{bot_userid}
updateBotById
/v3/bots/{bot_userid}
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your SendBird Chat Platform API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'schedule an announcement' or 'create a bot', and Jentic returns the matching SendBird Chat Platform API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Specific to using SendBird Chat Platform API through Jentic.
What authentication does the SendBird Chat Platform API use?
The SendBird Chat Platform API uses an API key passed in the `Api-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I schedule an announcement with the SendBird Chat Platform API?
Yes. Use the POST /v3/announcements endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SendBird Chat Platform API?
Rate limits are not specified in the OpenAPI spec. Check the SendBird documentation for the limits that apply to your plan.
How do I schedule an announcement through Jentic?
Install self-hosted Jentic One, import the SendBird Chat Platform API from the API Directory, and store your `Api-Token` once. Your agent then searches for 'schedule an announcement', gets back the POST /v3/announcements operation with its input schema, and executes the call with the credential injected at execution time.
Is there a SendBird Chat Platform API MCP server?
You don't need an MCP server to give your agent the SendBird Chat Platform API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.
How many endpoints does the SendBird Chat Platform API have?
The SendBird Chat Platform API exposes 92 endpoints across nine resource groups: users, group channels, open channels, messages, bots, announcements, moderation, metadata and statistics.
Can I limit what my agent is allowed to do with the SendBird Chat Platform API?
Yes. Because Jentic One is self-hosted, your own rules decide which SendBird operations and credentials the agent may use. Since the bot id sits in the URL path at /v3/bots/{bot_userid}, you can pin the agent to a single bot so it only views and updates that bot and adds it to channels via POST /v3/bots/{bot_userid}/channels. You choose the operations it may call, so destructive ones like bot deletion (DELETE /v3/bots/{bot_userid}) are excluded unless you explicitly add them.
Where is the official OpenAPI spec for the SendBird Chat Platform API?
SendBird ships one inside its Java platform SDK repository, at `https://raw.githubusercontent.com/sendbird/sendbird-platform-sdk-java/main/api/openapi.yaml`. That document is OpenAPI 3.0.3, titled 'Sendbird Platform SDK' version 1.0.0, and covers 53 paths and 92 operations; SendBird's own Platform API overview page links the repository that holds it. The version in the Jentic API Directory covers the same 92 operations and also declares the `Api-Token` security scheme, which SendBird's document leaves out even though its setup guide states that a master or secondary API token is required on API requests.
deleteBotById
/v3/bots/{bot_userid}/channels
joinChannels
/v3/bots/{bot_userid}/channels
botLeaveGroupChannels