For Agents
Send messages, fetch chat history, create channels, manage channel membership, and look up users on the Flock team-messaging platform.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flock 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 Flock API API.
Send a chat message to a Flock channel or direct user
Fetch the recent message history of a channel for analysis or display
Create a new channel with a name and a list of initial members
Add or remove members from an existing channel
GET STARTED
Use for: Send a message to the engineering channel, Fetch the last 50 messages in a channel, Create a new channel for the launch project, Add three users to an existing channel
Not supported: Does not handle voice or video calls, file sharing, or external email - use for Flock channel and direct messaging, channel management, and user lookups only.
The Flock API exposes the team-messaging surface of the Flock workplace chat platform. It uses FlockOS-style methods accessed through POST requests with a query-parameter token, covering channels, chat messages, contacts, and user profiles. The API supports sending messages, fetching message history, creating channels, and managing channel membership.
List the members of a channel for audit and notification flows
Look up a user's profile or public profile by user ID
Patterns agents use Flock API API for, with concrete tasks.
★ Workflow notifications into team channels
Internal tools and automations call /chat.sendMessage to post structured updates into Flock channels - deployment notices, alert summaries, or daily digest messages. The same endpoint handles both channel and direct messages, so a single integration covers personal and team notifications.
Send a deployment-success message with the build ID to channel #engineering
Channel and membership management
HR and ops tools create per-project channels, seed them with the right members, and clean up when the project ends. /channels.create, /channels.addMembers, and /channels.removeMembers cover the full lifecycle, while /channels.listMembers backs audit dashboards that confirm who currently has access to each space.
Create channel #project-launch and add five named user IDs as members
Conversation history analysis
Analytics and search tools call /chat.fetchMessages to pull recent message history for a channel and feed it into summarisation, search, or compliance pipelines. Combined with /users.getInfo and /roster.listContacts, the API provides enough context to attribute each message to a named team member.
Fetch the last 100 messages from channel C123 and resolve each sender ID to a display name
AI agent team assistant
An AI assistant uses Flock through Jentic to answer natural-language requests such as 'summarise the engineering channel today' or 'invite Alice to the launch channel'. Jentic returns the right Flock method per intent so the agent does not need to learn the FlockOS POST-with-query-token convention before issuing calls.
Fetch today's messages from channel C123, summarise them, and post the summary back into the same channel
11 endpoints — the flock api exposes the team-messaging surface of the flock workplace chat platform.
METHOD
PATH
DESCRIPTION
/chat.sendMessage
Send a message to a channel or user
/chat.fetchMessages
Fetch recent messages from a channel
/channels.list
List channels accessible to the token
/channels.create
Create a new channel
/channels.addMembers
Add members to a channel
/channels.removeMembers
Remove members from a channel
/users.getInfo
Look up a user's profile information
/chat.sendMessage
Send a message to a channel or user
/chat.fetchMessages
Fetch recent messages from a channel
/channels.list
List channels accessible to the token
/channels.create
Create a new channel
/channels.addMembers
Add members to a channel
Three things that make agents converge on Jentic-routed access.
Credential isolation
Flock API tokens are stored encrypted in the Jentic vault and appended to the request as the 'token' query parameter at execution time, so the raw token never enters the agent context.
Intent-based discovery
Agents search Jentic by intent such as 'send a message to a Flock channel' and Jentic returns the matching FlockOS method with its input schema, so the agent does not need to learn the POST-with-query-token convention before issuing calls.
Time to first call
Direct Flock integration: half a day to a day for FlockOS method calling, query-token handling, and pagination of message fetches. Through Jentic: under 1 hour to search, load the schema, and execute.
Alternatives and complements available in the Jentic catalogue.
Slack Web API
Slack is the dominant team-messaging API with a much larger surface than Flock
Pick Slack when the team already uses it; pick Flock when the workspace is on Flock and the agent must work within FlockOS conventions
Discord API
Discord is community-focused chat that overlaps with Flock for messaging primitives
Choose Discord for community spaces; choose Flock for internal team messaging on the Flock platform
Mattermost API
Mattermost is a self-hosted alternative for team messaging
Pick Mattermost when the deployment is self-hosted; pick Flock when the workspace runs on Flock's cloud
Specific to using Flock API API through Jentic.
What authentication does the Flock API use?
The Flock API uses an API token passed as a 'token' query parameter on each POST request. Through Jentic the token is held in the encrypted vault and appended at execution time, so the raw token never enters the agent context.
Can I send a message to a channel with the Flock API?
Yes. POST to /chat.sendMessage with the channel ID and message text. The same endpoint handles direct messages by passing a user ID instead of a channel ID.
How do I create a new Flock channel and add members?
Call POST /channels.create with the channel name to create the channel, then POST /channels.addMembers with the channel ID and an array of user IDs to seed it with the right members.
What are the rate limits for the Flock API?
Flock does not document a fixed global rate limit in the spec. Limits are applied per token. Treat 429 responses as the source of truth and back off using the Retry-After header.
How do I post a Flock message through Jentic?
Search Jentic for 'send a Flock message', load the schema for /chat.sendMessage, and execute the call with the channel ID and text. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.
Can I fetch message history with this API?
Yes. POST to /chat.fetchMessages with a channel ID and pagination cursor to retrieve recent messages.
/channels.removeMembers
Remove members from a channel
/users.getInfo
Look up a user's profile information