# Flaghand vs Ocoya for posting with AI agents

Ocoya combines AI copy, visuals, campaigns and workflow automation with social scheduling. It also offers a REST API
and a hosted MCP server. Flaghand is a narrower publishing desk for an agent you already use: the agent prepares the
posts, but only the owner can authorize publication with a passkey.

**Checked on October 26, 2026.** Ocoya facts come from its own [pricing page](https://www.ocoya.com/pricing),
[product overview](https://www.ocoya.com/), [campaign features](https://www.ocoya.com/features/campaigns),
[API reference](https://docs.ocoya.com/api-reference), [MCP setup](https://docs.ocoya.com/mcp/get-started),
[MCP tool catalog](https://docs.ocoya.com/mcp/tools) and
[create-post tool](https://docs.ocoya.com/mcp/tools/ocoya-create-post).
These are public-page checks, not a hands-on trial. Prices and features can change; recheck those sources before buying.

## The short answer

- **Choose Ocoya** if you want one app to generate copy and visuals, build multi-post campaigns and automate work across
  social networks and other services. Its MCP lets an external agent work with that publishing system too.
- **Choose Flaghand** if your own agent already writes and you want its credential to be incapable of approving,
  scheduling or publishing. The owner signs off on the exact posting snapshot inside Flaghand.

## Where Ocoya is better

- **Built-in AI and design.** Ocoya takes a prompt, URL or objective and generates captions, visuals and hashtags. Its
  overview describes reusable brand guidance for tone, colours, fonts and audience, along with copy in 37 languages.
  Flaghand leaves writing to your own agent; it doesn't bundle an AI writer.
- **Campaign creation.** Ocoya can generate a sequence of network-adapted social drafts across a date range, then let you
  review the batch or edit individual posts before distribution. It also generates blog campaigns; Flaghand isn't a blog
  publishing or campaign-generation service.
- **More destinations.** Ocoya lists Facebook Pages, Instagram, X, LinkedIn profiles and company Pages, Pinterest,
  Bluesky, Threads, TikTok, YouTube Shorts, Google Business, Mastodon and others. Flaghand focuses on X and LinkedIn
  personal profiles; TikTok remains subject to TikTok's review.
- **Connected workflows.** Ocoya advertises visual automations and an inbox for messages, comments and mentions. Its
  example turns a new WooCommerce product into social content. Flaghand's draft/check/approve loop isn't a replacement
  for that broader automation and engagement suite.
- **Available to try now.** Ocoya advertises a seven-day trial. Flaghand is in early access and public sign-up isn't
  open yet.

## Pricing and access

Ocoya's US-dollar pricing page shows the following **monthly-billed** plans. VAT applies where applicable.

| Plan | Monthly payment | Users | Social profiles | Monthly AI credits |
|---|---|---|---|---|
| Starter | $29 | 1 | 5 | 300 |
| Team | $79 | 5 | 20 | 1,500 |
| Agency | $199 | 20 | 100 | 5,000 |

The trial requires a card and renews at the selected price unless canceled. The yearly selector advertises two months
free; the default public view checked here doesn't expose annual totals, so this guide doesn't guess an annual bill.
Credits renew monthly. The campaign page says one credit per generated post or article; don't assume every other AI
operation consumes credits at that same rate. Custom arrangements are offered above Agency.

All three plan cards advertise 28 integrations. Those aren't 28 interchangeable social publishing networks: the catalog
also includes CMS, commerce, database and messaging connections, and marks Framer as beta. Check the destination and
format your workflow needs. The cited API and MCP pages don't establish a separate plan-by-plan access matrix, so this
guide doesn't promise every tool is included on Starter.

This guide doesn't quote a Flaghand price while its public sign-up and pricing remain closed.
[Get access to Flaghand](/schedule) is the current entry point.

## How the AI drafts

Ocoya's social campaign mode takes an outcome, audience and date range and produces unpublished drafts with captions
and visuals. You can revise an individual post or approve a batch for its planned sequence. Its MCP also exposes
`ocoya_create_ai_post` and `ocoya_create_ai_campaign`: the latter starts asynchronous generation, so a generating result
isn't a completed or published campaign.

Flaghand uses the writing agent you bring. An agent can work from your source material, upload media, create drafts,
check them and request your approval through the API or MCP. It proposes a time; that proposal alone creates no
scheduled job. See the [agent documentation](https://app.flaghand.com/docs/agents) and
[live OpenAPI spec](https://app.flaghand.com/api/v1/openapi.json).

## API and MCP access

Ocoya's REST API accepts an API key through `X-API-Key` or Bearer authentication. Its MCP endpoint is
`https://mcp.ocoya.com`, using browser OAuth. You sign in, review the requested permissions and choose which brands the
connection can access. The docs cover clients including Claude, ChatGPT, Codex and VS Code.

Its tools can read accounts and calendars, generate drafts and campaigns, edit posts, attach media, schedule, publish
immediately and run workflows. That is a real agent interface, not just a built-in caption writer. Its permission names
matter: `posts:write` covers drafting, editing, deleting **and scheduling**; `posts:publish` permits immediate publication.
Withholding immediate-publish permission therefore isn't the same as a draft-only connection.

Flaghand OAuth MCP connectors receive `read`, `drafts`, `media` and `request-approval`. No API token scope can approve,
schedule or post, on any plan. An agent can request the owner's decision, not grant it. The distinction is credential
authority, not whether the products have MCP or use OAuth.

## Does a person approve each post?

**Ocoya describes review, but not a universal per-post approval boundary.** Its campaign page says generated content
starts as drafts and lets you approve the batch or edit posts before distribution. Its MCP setup advises reviewing
consequential write actions, especially immediate publishing, deletion and workflow changes.

However, `ocoya_create_post` can save a draft with no time, schedule one with `scheduledAt`, or publish with
`publishNow: true`. The cited tool and setup pages don't establish a mandatory separate human approval over every
API/MCP-created post or an immutable, passkey-signed snapshot. We haven't tested workspace-specific review rules. It
would be wrong to claim Ocoya has no review, or to assume authorizing an OAuth connection means a person has approved
each future post.

**Flaghand requires the owner's passkey.** Approval freezes the account, time, text, media, alt text and outgoing request
into a snapshot. Flaghand hashes it with SHA-256 and records the owner's passkey signature over that hash. Changing the
posting content, account or time needs a new approval, and the scheduler checks the signed snapshot again just before
posting. Its X and LinkedIn previews are drawn to match the real sites. That mandatory owner step is useful if you want
an agent to prepare work without authorizing publication; it isn't fully unattended publishing.

## After publication

Flaghand reads X posts back and compares available text, author, reply chain, media count and alt text with the approval.
It doesn't verify link destinations or media-file identity/bytes, and LinkedIn read-back isn't available. The Ocoya
pages cited here don't document this kind of comparison against a passkey-signed posting snapshot.

## Side by side

| | Ocoya | Flaghand |
|---|---|---|
| Main strength | AI copy and visuals, campaigns, more networks and visual automation | Publishing desk for your own agent with owner-only authorization |
| Monthly-billed plans | Starter $29; Team $79; Agency $199, plus applicable VAT | Early access; public sign-up not open yet |
| AI drafting | Built-in generation and campaigns, with credits | Bring your own agent |
| Networks | Broad social, CMS and messaging catalog; not every integration is a social network | X and LinkedIn personal profiles; TikTok subject to review |
| API and MCP | REST API keys; hosted OAuth MCP with brand and permission selection | Public API/OpenAPI and OAuth or token MCP |
| Human review | Campaign draft/batch review; universal API/MCP per-post enforcement not established by cited docs | Mandatory owner passkey over exact snapshot; tokens cannot approve |
| Can an agent schedule? | Yes, with `posts:write`; immediate publishing uses `posts:publish` | No API token scope permits scheduling or posting |

## Bringing your drafts

If you can save your posts as CSV or JSON, Flaghand's
[migration recipe](https://app.flaghand.com/docs/agents#migrate-from-another-scheduler) describes its generic file format. Imports create
drafts, with old times as proposed times, not jobs or transferred approvals. This is not a one-click Ocoya migration,
and importing doesn't pause Ocoya's queue. The owner must decide the cutover; the CLI isn't on npm yet.

## Try Flaghand

Read [How to let an AI agent post safely](/docs/guides/let-an-ai-agent-post-safely) for questions to ask of either tool.
[Get access to Flaghand](/schedule).

[All guides](/docs/guides.md)