Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Autoposting 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%2Fautoposting.ai%2Fautoposting" | 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%2Fautoposting.ai%2Fautoposting" | 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 Autoposting API.
Create, schedule, and publish posts to X, LinkedIn, Instagram, Threads, and YouTube
Rewrite and score post content with AI before publishing
Generate carousels and short video clips from source material
Run autonomous posting agents on a schedule and review their outputs
Organise brand workspaces and connect each platform's OAuth tokens for publishing
GET STARTED
Patterns agents use Autoposting API for, with concrete tasks.
★ AI Agent Social Publishing via Jentic
An agent that manages a social presence can call Autoposting through Jentic without wiring the API key or juggling per-platform OAuth. The agent searches by intent, receives the operation schema, and drafts, schedules, or publishes a post across platforms. This fits marketing agents and content pipelines that produce and distribute posts programmatically.
Search Jentic for 'schedule a social post', load the operation schema, draft the post, and queue it for the chosen platforms
Cross-Platform Post Scheduling
Draft a post once and schedule it to publish across X, LinkedIn, Instagram, Threads, and YouTube. Autoposting stores the draft, holds it on a schedule, and publishes it to the platforms set on the post, so an agent can run a content calendar without a separate scheduler per network.
Call POST /posts to create a post, then PUT /posts/{postId}/schedule to queue it
AI Content Generation
Produce carousels, short clips, and refined copy from source material. Autoposting generates carousel content and designs, cuts clips from longer video, and rewrites or scores draft copy, so a marketing agent can turn a brief or a recording into ready-to-post assets.
Call POST /carousels/generate to produce carousel content from a topic
Autonomous Posting Agents
Create agents that produce and post content on a schedule, then review their runs and outputs. Autoposting lets an operator spin up an agent, trigger an immediate run, and inspect what it generated, so a team can automate a recurring posting cadence with a human reviewing results.
Call POST /agents to create an agent, then POST /agents/{agentId}/run to trigger a run
187 endpoints — the autoposting api schedules, publishes, and ai-enhances social content across x, linkedin, instagram, threads, and youtube.
METHOD
PATH
DESCRIPTION
/posts
Create a new post
/posts/{postId}/schedule
Schedule a post
/posts/{postId}/publish
Publish a post immediately
/posts/{postId}/rewrite
AI rewrite post content
/carousels/generate
AI-generate carousel content
/clips/{clipId}/publish
Publish a clip to platforms
/agents
Create an AI posting agent
/brands
List brands
/posts
Create a new post
/posts/{postId}/schedule
Schedule a post
/posts/{postId}/publish
Publish a post immediately
/posts/{postId}/rewrite
AI rewrite post content
/carousels/generate
AI-generate carousel content
/clips/{clipId}/publish
Publish a clip to platforms
/agents
Create an AI posting agent
/brands
List brands
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Autoposting API by hand means managing its API key (a Bearer token or the x-api-key header), connecting each platform's OAuth tokens per brand, and sequencing create, schedule, and publish calls yourself. Through Jentic you install once, import Autoposting from the API Directory, store the key once, and your agent calls it.
Permission scoping
Autoposting puts the brand slug and post id in the URL path (/brands/{brandSlug}, /posts/{postId}), so a rule can pin your agent to one brand and the post operations you choose. You choose the operations it may call, so you can allow drafting and scheduling while leaving immediate publish or delete out.
Credential isolation
Your Autoposting 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 'generate a carousel', and Jentic returns the matching Autoposting 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 Autoposting API through Jentic.
Is there an Autoposting MCP server?
You don't need a separate MCP server to give your agent the Autoposting API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the draft, schedule, publish, and generate operations it needs.
Can I limit what my agent is allowed to do with the Autoposting API?
Yes. Write a rule that allows drafting and scheduling posts for one brand slug, so the agent can prepare and queue content for that brand while publishing immediately or deleting posts stays out of reach. Every call is logged by your self-hosted instance.
What authentication does the Autoposting API use?
The Autoposting API authenticates with an API key sent as a Bearer token in the Authorization header or in the x-api-key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I schedule posts across multiple platforms with the Autoposting API?
Yes. Create a post and schedule it, and the platforms it targets, such as X, LinkedIn, Instagram, Threads, and YouTube, are set on the post itself. The API also rewrites and scores content and generates carousels and clips.
What are the rate limits for the Autoposting API?
The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://autoposting.ai for current limits and plan tiers.
How do I schedule a social post with the Autoposting API through Jentic?
Search Jentic for 'schedule a social post' and it returns the Autoposting operations with their input schemas; the agent drafts the post and queues it for the chosen platforms. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Draft, schedule, publish, rewrite, and score social posts across X, LinkedIn, Instagram, Threads, and YouTube, and generate carousels and clips. Returns structured JSON over a REST API authenticated with an API key.
Use for: I want to schedule a post to LinkedIn and Instagram, Publish a post to X right now, Generate a carousel from a topic, Rewrite a draft post for a different tone
Not supported: Does not run paid ad campaigns, send email or SMS, or host video files for playback. Use for scheduling and publishing organic social content only.
The Autoposting API schedules, publishes, and AI-enhances social content across X, LinkedIn, Instagram, Threads, and YouTube. It drafts, schedules, publishes, rewrites, and scores posts, and generates carousels and short video clips from source material. Autonomous posting agents, brand workspaces, knowledge bases, and per-platform OAuth connections round out the surface, all behind a consistent success-and-data response envelope.
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>