Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SocialBee 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsocialbee.io%2Fsocialbee" | shStep 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%2Fsocialbee.io%2Fsocialbee" | 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 SocialBee API.
Create post
List posts
Get post
Update post
Delete post
Patterns agents use SocialBee API for, with concrete tasks.
GET STARTED
★ Social Media Operations
Use the SocialBee API to perform social media operations programmatically. The API provides 9 endpoints covering core functionality including create post, list posts, get post.
Call POST /posts to create post
Automated Categories Management
Automate categories operations by combining multiple SocialBee API endpoints. Agents can list posts and then get post in a single workflow.
Call GET /posts to list posts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SocialBee 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 API documentation or handle apiKey tokens manually.
Search Jentic for 'create post', load the operation schema, and execute with Jentic-managed credentials
9 endpoints — socialbee social media management api for managing posts, categories, profiles, and scheduling.
METHOD
PATH
DESCRIPTION
/posts
Create post
/posts
List posts
/posts/{postId}
Get post
/posts/{postId}
Update post
/posts/{postId}
Delete post
/categories
Create category
/categories
List categories
/profiles
List profiles
/posts
Create post
/posts
List posts
/posts/{postId}
Get post
/posts/{postId}
Update post
/posts/{postId}
Delete post
/categories
Create category
/categories
List categories
/profiles
List profiles
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SocialBee API by hand means passing your API key in the Authorization header, pointing at the app.socialbee.io/api host, and coordinating posts, categories, and profiles yourself. Through Jentic you install once, import the SocialBee API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The SocialBee API identifies work by operation rather than a durable resource id you would scope on, so limit the agent to the operations it needs, such as creating or listing posts. You choose that set, so destructive ones like deleting a post are only included if you add them.
Credential isolation
Your SocialBee API key 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 a social post' or 'list content categories', and Jentic returns the matching SocialBee API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SocialBee API through Jentic.
What authentication does the SocialBee API use?
The SocialBee API uses an API key passed in the `Authorization` 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 create post with the SocialBee API?
Yes. Use the POST /posts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SocialBee API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create post through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create post'. Jentic returns the matching SocialBee API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SocialBee API have?
The SocialBee API exposes 9 endpoints covering categories, posts, profiles operations.
Can I limit what my agent is allowed to do with the SocialBee API?
Yes. Because you run Jentic One yourself, your own rules decide which SocialBee API operations and credentials the agent can use. The SocialBee API is scoped by operation rather than a durable resource id, so you grant only the calls the agent needs, such as creating posts (POST /posts) or listing posts and categories (GET /posts, GET /categories). Destructive operations like deleting a post (DELETE /posts/{postId}) are included only if you choose to add them.
For Agents
Programmatically create post, list posts. Covers 9 operations with apiKey authentication.
Use for: I need to post, I want to posts, Search for post, Find all post
Not supported: Does not handle payments, communications, or crm - use for social media only.
SocialBee social media management API for managing posts, categories, profiles, and scheduling. The API exposes 9 endpoints secured with apiKey authentication.