Your team
Set the brief, campaign goal, accounts, and boundaries.
01Direction
AI agent
Resolve the workspace, connected accounts, and available media.
Put your AI agent on the social media team.
Postqued gives people and AI agents the same place to plan, review, publish, and check results. Your team keeps control of accounts, permissions, and approvals while the agent handles repeatable work.
One shared workflow
The agent does the legwork. Your team stays at the decision points.
Both sides work against the same client workspace, connected accounts, content, revisions, and publishing history. There is no second calendar to reconcile.
Your team
Comment on the exact revision and approve when it is ready.
02Review
AI agent
Prepare the post, apply feedback, and validate the final payload.
Your team
Confirm the destinations and publish time before it goes live.
03Delivery
AI agent
Schedule the approved work and follow its status to completion.
What the agent can do
Useful actions across the whole campaign—not just a publish button.
Postqued exposes the work around publishing as well as publishing itself, with explicit limits for analytics and engagement coverage.
Prepare the campaign
Resolve the right workspace and accounts, upload or reuse media, create posts, and set platform-specific publishing options.
Work through review
Submit revisions, leave comments, suggest caption changes, request updates, and keep approval tied to the version people reviewed.
Publish with safeguards
Validate the request first, confirm the destination and timing, use safe retries, and follow each publishing job to a durable result.
Check what happened
Read supported analytics and work with comments and replies without losing the organization and workspace boundaries around the task.
Control before consequenceReview current product boundaries
Automation you can inspect before it acts.
A useful social agent should make routine work faster without making account scope, approval state, or delivery status harder to see.
Resolve the organization, workspace, and accounts first.
Validate the exact platform payload with a dry run.
Keep feedback and approval tied to the current revision.
Use idempotency for retries and inspect durable status.
Agent runLaunch campaign
- Workspace resolvedLuma Skincare
- Accounts checkedInstagram · LinkedIn · TikTok
- Dry run passed3 platform payloads validated
- Waiting for confirmationExact revision and publish time shown
- 5Schedule and check statusRuns after confirmation
Where it fits
Use an agent without inventing a separate operating model.
Social teams
Let the agent handle setup, not judgment.
Use an agent for repetitive account lookup, media preparation, validation, scheduling, and status checks while people keep control of direction and approval.
Agencies
Keep every client in the right workspace.
Separate accounts, content, collaborators, and client review by workspace so an agent can help without mixing one brand's work into another.
Developers
Use the API directly or give the tools to an agent.
Build deterministic jobs with REST API v2, connect compatible agents through MCP, or use both against the same Postqued organization.
Choose the connection
This page explains the workflow. These pages help you wire it up.
Use MCP for tool discovery in compatible agents, REST for direct application code, or the OpenClaw skill for a packaged setup.
For compatible agents
Remote MCP server
Connect Claude Desktop, Claude Code, Cursor, or another compatible client to 62 actions with one organization-bound API key.
Configure MCPFor application code
REST API v2
Call the documented upload, publishing, analytics, engagement, approval, and collaboration endpoints from your own backend.
Read the API docsFor OpenClaw
Installable agent skill
Install the Postqued skill, attach your API key, and give OpenClaw the operating instructions for safe social publishing.
Set up OpenClawQuestions and answers
What teams ask before connecting an agent.
Specific answers about capabilities, access, networks, safeguards, and pricing.
What can an AI agent do with Postqued?
A compatible AI agent can use Postqued tools for workspaces, connected accounts, media, publishing, analytics, comments and replies, approvals, suggestions, team collaboration, and client review. The current remote MCP catalog contains 62 actions.
How is this page different from the Postqued MCP page?
This page explains how people and AI agents work together in Postqued. The MCP page is the technical setup page for connecting a compatible client, downloading the agent skill, and reviewing the complete tool catalog.
Can an AI agent publish without a person reviewing the post?
Postqued supports direct API and MCP publishing for authorized workflows, but consequential actions should use a dry run and explicit confirmation. Teams can also place revision-aware internal or client approval before publishing.
Which social networks can an AI agent publish to through Postqued?
Postqued publishes to TikTok, Instagram, Facebook, Threads, LinkedIn, YouTube, X, Pinterest, Mastodon, and Bluesky. Each network still has its own account, media, format, and provider requirements.
Does every Postqued plan include API and MCP access?
Yes. API and MCP access are included on every paid plan. Postqued starts at $9 per month for five connected accounts and offers a seven-day trial; there is no permanent free plan.
Does the AI agent get access to every Postqued workspace?
No. Agent actions remain subject to the organization, workspace, role, and credential scope available to the connected account. Resolve the intended workspace before taking action and keep credentials server-side and revocable.
People set direction. Agents move the work.
Give your AI agent a social workflow your team can see.
Start with the shared workspace, then connect through MCP or REST when you are ready.