Guides · Updated

Flaghand vs Agorapulse for teams that review posts

Agorapulse is a social media suite for publishing, answering messages and reporting across many networks. Flaghand is a smaller publishing desk for people and their own AI agents. Both let a person review a draft before it goes out; the difference is what happens to that approval if someone changes the post afterwards.

Checked on October 26, 2026. Every Agorapulse fact here comes from its own pricing page, approval workflow guide, sending for approval guide, reviewer guide, MCP guide, Open API overview and API connection guide. Prices and features change. This is a public-documentation comparison, not a signed-in product test.

The short answer

What Agorapulse costs

These are US-dollar list prices per user per month, not the price for the whole team:

Plan Paid monthly Monthly equivalent, billed annually Approval features
Standard $99 $79 No simple approval workflow
Professional $149 $119 Simple, one-step approval workflows
Advanced $199 $149 Simple workflows and bulk approval
Custom Tailored pricing Tailored pricing Multi-step approval workflows

Standard, Professional and Advanced each include 10 social profiles; Custom lists unlimited profiles. Extra profiles cost more. X publishing is listed as a separate X Lite or X Plus add-on, with its price available on request, so don't treat the subscription price as the complete cost of an X setup.

For example, three Professional seats at the annual rate are $357 a month equivalent, or $4,284 a year, before taxes and add-ons. Flaghand is in early access: public sign-up is not open yet and its pricing is not public.

Where Agorapulse is better

How Agorapulse review works

The author prepares the post with a date and time, selects reviewers or a workflow, adds an optional message, and sends it for approval. Internal reviewers need suitable profile permissions; external reviewers use a Shared Calendar. The author can require every selected reviewer to approve.

An internal reviewer opens the assigned post and chooses Approve for all and save or Request changes. An external reviewer opens the post group and chooses Approve or requests changes. Approval schedules the post for its chosen time, or advances it to the next workflow stage. An unapproved post is blocked at its scheduled time; Agorapulse notes that approval within the next five minutes may still let it publish, but does not guarantee that.

That is useful human review. It is not the same as making an approved version immutable.

Does approval cover the exact text and media?

Agorapulse: a person reviews the composed post, but its workflow guide explicitly lets profile Admins and Editors unlock a locked post using Edit this post and save changes. After a completed workflow, the post stays Approved; during a workflow, it stays on the same step. So approval status alone does not prove the current text and media are unchanged from the version the reviewer saw. The cited pages do not describe a passkey signature over a content hash or a final cryptographic check of that approved version before sending.

Flaghand: the agent checks each draft and requests approval through the desk. The owner reviews every post's account, time, text, media and alt text. One passkey tap can approve the whole plan, but covers each post's snapshot: Flaghand hashes the snapshots with SHA-256 and verifies the owner's signed assertion. The snapshot includes the exact platform request. Changing posting content, media, account or time requires a new approval; the scheduler checks the signed snapshot again immediately before sending. Internal labels and notes are not posting content.

The approval reference explains that boundary. It does not mean the owner must approve posts one at a time, or that the software can prove they read every word.

API and MCP access

Agorapulse has an official remote MCP connector, currently in beta, on all plans except Legacy. Its guide covers Claude, ChatGPT and Microsoft Copilot, subject to those clients' subscription and configuration requirements. It can read social data, generate drafts and add calendar notes. For new posts, it does not automatically publish: drafts must be scheduled and published inside Agorapulse. Do not mistake that for an entirely read-only connector: it also documents sending inbox replies, subject to an organization's inbox approval workflow when one is configured.

Its Open API requires Custom. The overview describes analytics, listening, inbox operations, calendar notes and media uploads, and mentions creating drafts. The connection guide still calls the API read-only, despite describing write operations. Those public pages are inconsistent; neither cited guide documents a general post scheduling or publishing endpoint. If API publishing is essential, these pages are not enough to promise it.

Flaghand's agent documentation and OpenAPI spec are public. Its API and MCP let an agent upload media, create or edit drafts, check them, request approval and read results. OAuth connectors receive read, drafts, media and request-approval. No API token scope can approve, schedule or post; owner approval routes refuse tokens regardless of scope. The CLI is not on npm yet; the hosted MCP does not require it.

Side by side

Agorapulse Flaghand
Best fit Multi-network team publishing, inbox and reports A person's agent prepares posts; an owner approves the exact plan
Entry price Standard $99 per user monthly, or $79 equivalent billed annually Early access; public sign-up and pricing not open
Team approval entry Professional $149 monthly, or $119 equivalent billed annually, per user Owner passkey approval; editors cannot approve
Approval stages One-step from Professional; multi-step on Custom One owner decision over each snapshot, optionally as one plan
Edit after workflow approval Authorized edits can leave the post Approved Posting-content changes need a new approval
New-post MCP writes Drafts; schedule and publish in Agorapulse Drafts, checks and approval requests; never approval or publication
Public API Custom; public guides have conflicting read/write descriptions Public reference; workspace-scoped token access
Shared inbox and reports Yes No shared inbox or cross-network report builder

After it posts

Flaghand reads X posts back and compares normalized text, author, hidden reply mentions, media count, available alt text, reply chain and quote with the approved expectations. It does not verify link destinations or media-file bytes. LinkedIn posts are not read back. Agorapulse offers post reports; the sources above do not document this kind of comparison against an approved snapshot. A successful publish or an engagement report is not that comparison.

Try Flaghand

Start with the agent documentation, or use the safety checklist to compare any publishing tool. Get access to Flaghand. For its current TikTok restrictions, see Flaghand and TikTok.