Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ContentStudio API v1, 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%2Fcontentstudio.io%2Fcontentstudio" | 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%2Fcontentstudio.io%2Fcontentstudio" | 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 ContentStudio API v1 API.
Schedule and publish posts to connected Facebook, Bluesky, and Google Business Profile accounts
Pull per-network analytics such as Facebook summary KPIs, audience growth, and top posts
Reply to comments and direct messages from a unified social inbox
Run evergreen and RSS automations that recycle and auto-post content
GET STARTED
Organize publishing with campaigns, labels, and content-category posting slots
Generate AI images and video for posts within a workspace
Patterns agents use ContentStudio API v1 API for, with concrete tasks.
★ Agent-run social publishing
An AI agent connected through Jentic can draft a post, create it with createPost, and schedule it to several connected accounts in one workspace without a human opening the ContentStudio dashboard. The agent reads back post status with fetchPosts and can pause publishing for the workspace if drafts need review.
Create a post for the connected Facebook and Bluesky accounts scheduled for 09:00 tomorrow, then fetch the post to confirm its scheduled status
Cross-network performance reporting
Marketing teams pull summary KPIs, audience growth, and top posts for each connected network to build a weekly report. ContentStudio exposes Facebook, Bluesky, and Google Business Profile analytics as separate endpoints so an agent can assemble a per-network rollup for the current period versus the previous one.
Pull the Facebook summary KPIs and audience-growth trend for the workspace and summarize the change versus the previous period
Unified inbox response
Community managers triage comments, direct messages, and reviews from one inbox instead of switching between native apps. An agent can list inbox elements, send a reply to a comment or direct message, hide spam comments, and reply to reviews, all within a single workspace.
Find the newest unanswered comment in the inbox and post a reply, then mark the conversation as done
356 endpoints — the contentstudio api schedules and publishes posts to connected social accounts, including facebook, bluesky, and google business profile, then tracks how each post performs.
METHOD
PATH
DESCRIPTION
/api/v1/workspaces/{workspace_id}/accounts
List connected social accounts in a workspace
/api/v1/workspaces/{workspace_id}/posts
Create a social media post
/api/v1/workspaces/{workspace_id}/posts
Fetch scheduled and published posts
/api/v1/workspaces/{workspace_id}/campaigns
Create a campaign
/api/v1/workspaces/{workspace_id}/analytics/facebook/summary
Read Facebook summary KPIs for the current period
/api/v1/workspaces/{workspace_id}/inbox/conversations/{conversation_id}/messages
Send a direct message from the inbox
/api/v1/workspaces/{workspace_id}/accounts
List connected social accounts in a workspace
/api/v1/workspaces/{workspace_id}/posts
Create a social media post
/api/v1/workspaces/{workspace_id}/posts
Fetch scheduled and published posts
/api/v1/workspaces/{workspace_id}/campaigns
Create a campaign
/api/v1/workspaces/{workspace_id}/analytics/facebook/summary
Read Facebook summary KPIs for the current period
/api/v1/workspaces/{workspace_id}/inbox/conversations/{conversation_id}/messages
Send a direct message from the inbox
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ContentStudio API by hand means minting an X-API-Key, learning the workspace-scoped path layout, and threading the workspace id through every call. Through Jentic you install once, import ContentStudio from the API Directory, store the key once, and your agent calls it.
Permission scoping
ContentStudio puts the workspace id in the URL path (/api/v1/workspaces/{workspace_id}/...), so a rule can pin your agent to one workspace. You choose the operations it may call, so destructive ones like removing a connected account or deleting a campaign are not included unless you add them.
Credential isolation
Your ContentStudio 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 'pull Facebook analytics', and Jentic returns the matching ContentStudio 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 ContentStudio API v1 API through Jentic.
What authentication does the ContentStudio API use?
The ContentStudio API authenticates with an API key sent in the X-API-Key header, per its OpenAPI spec. Through Jentic the key is stored once by your own self-hosted instance and injected when a call runs, so it never appears in the agent's prompt or logs.
Can I schedule posts to multiple networks with the ContentStudio API?
Yes. Create a post with the createPost operation under a workspace and target the connected accounts you want, such as Facebook, Bluesky, and Google Business Profile. You can fetch posts to confirm their scheduled status and pause publishing for the whole workspace while drafts are reviewed.
Can I limit what my agent is allowed to do with the ContentStudio API?
Yes. Write a rule that pins the agent to one workspace id in the URL path and allows only the operations you pick, for example creating posts and reading analytics, so it cannot remove connected accounts or delete campaigns, and every call it makes is logged.
What are the rate limits for the ContentStudio API?
The OpenAPI spec does not specify rate limits. Check the ContentStudio developer documentation at https://docs.contentstudio.io for current limits before running high-volume publishing jobs.
Is there a ContentStudio MCP server?
You don't need an MCP server to give your agent the ContentStudio API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls operations like createPost and fetchPosts on demand without loading another server's tool definitions into its context.
How do I publish a post with the ContentStudio API through Jentic?
Search Jentic by intent such as 'schedule a social media post', and Jentic returns the createPost operation with its input schema so your agent fills in the workspace, accounts, and content. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Schedule and publish social posts across connected accounts, pull per-network analytics, and reply to comments and direct messages from a unified inbox. Operations are grouped under a workspace.
Use for: Schedule a post to our Facebook and Bluesky accounts for tomorrow morning, Fetch last week's published posts and their status, Pull the Facebook summary KPIs for this workspace, Reply to the newest comment in the social inbox
Not supported: Does not handle ad campaign buying, link shortening, or website hosting. Use for social media publishing, analytics, and inbox management only.
The ContentStudio API schedules and publishes posts to connected social accounts, including Facebook, Bluesky, and Google Business Profile, then tracks how each post performs. It exposes per-network analytics such as summary KPIs, audience growth, and top posts, plus a unified inbox for replying to comments and direct messages. Content teams can group work into campaigns and labels, recycle posts with evergreen and RSS automations, and generate images or video for posts inside a workspace. Every operation is scoped to a workspace through the workspace_id path parameter.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>