Head to head · Social posting · October 2026 research run

Zernio (formerly Late) API + MCP vs Postiz API + MCP

Zernio (formerly Late) API + MCP scores 71.5 (BB) on agent readiness against Postiz API + MCP's 47.1 (D), and leads in 5 of 7 scored categories. Postiz API + MCP leads on schema & documentation and transparency & trust. Both do social posting.

Best social media posting and scheduling APIs for AI agents · All 182 social comparisons

Which one, for what

Zernio (formerly Late) API + MCP BB

Best for Agents and SaaS products that need posting, inbox and ads through one well-specified API with safe retries.

Ahead on

  • Reliability, 80 against 43
  • Agent ergonomics, 88 against 65
  • Security & auth, 65 against 49
  • Payments & pricing, 60 against 45

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

Breaking changes ship inside v1 on the day they're marked, 15 from 2 to 29 October 2026, while the changelog says they ship only as a new path version

Postiz API + MCP D

Best for Teams that want to self-host, or want 34 platforms including Mastodon, Farcaster, Discord and Slack on a flat plan.

Ahead on

  • Schema & documentation, 88 against 83
  • Transparency & trust, 82 against 71

Also in its favour

  • Open source

Watch for

20 security advisories between March and October 2026, including cross-tenant takeovers and file reads

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Zernio (formerly Late) API + MCP +37

Zernio (formerly Late) API + MCP 80

Better Stack page at zernio-status.com with components for the API, each network, schedulers, webhooks, inbox and analytics, read through its RSS feed (20). From 3 August to 1 November 2026 the feed lists many incidents, each partial by its own text. The longest touching the API, on 8 October from 14:44 to 15:52 UTC, had some customers see the dashboard and API slow or time out. On 19 October post creation failed for 21 minutes, and on 26 October many API requests failed for about 20 minutes. Reddit has been unavailable since 19 October because Reddit blocked third-party apps, and other items hit one network, the inbox or webhooks. No full outage of everything and nothing over an hour that wasn't partial, so minor only (20). Limits published by tier, 60, 600 or 1,200 requests a minute, a per-second analytics window and per-network posting caps (15). 429 carries Retry-After and X-RateLimit headers, and an Idempotency-Key covers posts and other writes (15). The terms state no SLA (0). GA (10). 20+20+15+15+0+10 = 80.

Postiz API + MCP 43

Scored for Postiz Cloud, since self-hosted uptime is the operator's. Postiz's terms (last updated 19 October 2026) say users may not use the Service, which includes the site and its sub-domains, to scrape it, so on 4 November postiz.com and its sub-domains were read only for robots.txt and the terms (paused, as bundle.social). Per the 1 October check, not re-read on 4 November, status.postiz.com is Gitroom's own page and showed our reader no components, so half the line, as scrapegraphai, youtrack and getty-images-mcp (10). That check found its history empty without being able to tell a clean record from a page that didn't render, and nothing is readable today, so the window is uncredited (5, as clickup and docusign; 10 before). 90 create-post requests an hour on every Cloud plan, per the 1 October docs and the throttler default of 90 in the source at v2.25.3 (15). Per the 1 October check, the docs don't mention Retry-After, the spec documents a 429 only for clipping, and there's no idempotency key (3). No SLA found (0). The public API isn't labelled beta (10). 10 + 5 + 15 + 3 + 0 + 10 = 43.

Agent ergonomics Zernio (formerly Late) API + MCP +23

Zernio (formerly Late) API + MCP 88

The tools page lists 20 core tools and says tools/list returns about 50 everyday ones, with search_tools and call_tool loading the long tail on demand (5 plus 10). Page and cursor pagination on list endpoints (20). ErrorResponse codes such as idempotency_conflict, and the MCP returns the list of accounts when account_id is ambiguous (18). Idempotency-Key with 24-hour keys and an Idempotent-Replayed header, plus readOnlyHint, destructiveHint and openWorldHint on tools (20). The SDKs page lists official clients in eight languages, including Node and Python (15). 15+20+18+20+15 = 88.

Postiz API + MCP 65

The docs say 13 MCP tools. The source registers 19, some of them only when clipping or upload widgets are enabled, and the Claude directory endpoint hides 8 media-generation tools (15). Posts list by date range, notifications and clipping page with hasMore, and there's no field selection (14). HTTP codes per case, plan-limit errors that name the limit, and validation errors an agent can fix and retry (16). Every MCP tool in source carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint. No idempotency key on REST (12). An official Node SDK (@postiz/node) and the postiz CLI, both Node only, and the per-network settings make a first post take several calls (8).

Security & auth Zernio (formerly Late) API + MCP +16

Zernio (formerly Late) API + MCP 65

API keys as Bearer tokens, restricted keys created through POST /v1/api-keys with any of ten resource groups switched off or limited to chosen profiles, and OAuth 2.1 with dynamic client registration on the MCP with eight scopes such as posts:read and analytics:read (30). Read-only keys and scopes are possible, members can be limited to profiles, and tools are annotated, but we found no approval guidance for publishing (14). The inbox, comments and DM tools return text from strangers and we found no prompt-injection guidance (0). A unified activity log endpoint (GET /v1/logs) covers publishing, connections, webhooks and messaging, webhook delivery logs are listed, X-Request-Id is on every response, and the security overview describes an append-only audit log of team-management actions for the owner. API calls aren't attributed to a key in a log we found (11). The DPA and pricing page say the SOC 2 Type II report and GDPR paperwork are available on request through the trust centre at trust.zernio.com. No security.txt (404 on 1 November) and no disclosure route, and the privacy contact is a named person's email (10). 30+14+0+11+10 = 65.

Postiz API + MCP 49

Per the 1 October check, not re-read on 4 November, Postiz uses one organisation API key, sent raw in the Authorization header and rotatable from settings. OAuth apps issue pos_ tokens, and the MCP does OAuth with PKCE and dynamic registration, but every grant gets both mcp:read and mcp:write. The docs also document the key in the URL path at /mcp/{key}, so less 10 (15). No read-only key or scope. Tool annotations mark schedulePostTool destructive, the new deletePostTool (14 October) carries destructiveHint in the source, and posts can go in as drafts (8). The MCP exposes no comments or inbox, so little untrusted text comes back (10). No audit log found, only notifications (2). SECURITY.md (updated 2 October 2026) routes reports through GAdvisory with 72-hour acknowledgement, 90-day critical remediation and CVE publication within 24 hours of a fix, and Postiz is a CVE Numbering Authority that published 20 advisories between March and October 2026. CI runs CodeQL. No bug bounty, certification or security.txt (14).

Payments & pricing Zernio (formerly Late) API + MCP +15

Zernio (formerly Late) API + MCP 60

No x402 or other machine payment (0). Per-unit prices published without login, per connected account a month, X calls passed through at X's rates and SMS per message (20). Two accounts free with no card (20). A person signs up in a browser for the first key. Keys can then be minted by API, which doesn't remove the human step (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Postiz API + MCP 45

No x402 or other machine payment (0). Cloud plan prices are public, with no per-call price (10). Self-hosting under AGPL-3.0 is free and includes the API and MCP, with no card. The Cloud trial's card policy isn't stated (20). Cloud needs a browser signup, and self-hosting needs a person to register developer apps with each network (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust Postiz API + MCP +11

Zernio (formerly Late) API + MCP 71

Closed API under published terms (last updated 9 October 2026), with the Node SDK under Apache-2.0 (15). The privacy policy, updated 26 October 2026, deletes data within 30 days of account deletion, keeps other data as long as needed, says content reached through the MCP or API isn't used to train models, and links a subprocessor list. A public DPA (19 October 2026, replacing a version dated 2 July 2026) is part of the terms with no signature needed, names ZERNIO SOFTWARE SL as processor, and deletes customer personal data within 10 business days of the end of the service, with backups within 30 days and logs within 90. The privacy policy also sets token lifetimes and deletion on disconnect for Google and Microsoft data. The statements agree, though general account data is kept as long as needed (26). No deprecation policy in practice. The changelog says a breaking change ships only as a new path version, yet breaking changes ship inside v1 on the day they're marked, and old getlate.dev URLs still redirect (6). The subprocessor list (9 October 2026) names 25 providers with purpose, data and transfer safeguard, and gives 14 days' notice of changes. Core hosting and the database are in London, and 18 entries say the location is provider-managed and not pinned to one region (15). 15+26+6+15 = 62.

Postiz API + MCP 82

AGPL-3.0 (30). Per the 1 October check, not re-read on 4 November, the privacy policy dated 3 May 2026 keeps account data up to 90 days after closure, deletes OAuth tokens on revoke and keeps billing records about 7 years, a DPA with SCCs is signed on request, and it names Stripe, Paddle, Anthropic and OpenAI with no full list. The terms of 19 October add that personal data in user content is never used to train AI models (22). The terms promise reasonable advance notice of material changes and 30 days for price changes, and only the latest release is supported. No API deprecation policy (8). Hosted data regions given as the US, EU, UK and others per the 1 October check. In the source at v2.25.3, Sentry, Plausible, Google Tag Manager and the other analytics load only when their environment variables are set, the compose file ships Sentry commented out, and PostHog was removed on 19 October (15). 30 + 22 + 8 + 15 = 75.

Schema & documentation Postiz API + MCP +5

Zernio (formerly Late) API + MCP 83

OpenAPI 3.1 at zernio.com/openapi.yaml, API version 1.431.1 on 1 November with 761 paths (25). llms.txt and Markdown pages (10). The MCP has a docs_search tool and annotated tools. We didn't read tool descriptions in source (12). Inputs typed in the spec with resource groups and enums (12). A shared ErrorResponse with a machine code and message, X-Request-Id on responses, examples on operations (12). Dated public changelog with JSON and RSS feeds and a changelog API, but breaking changes ship inside v1, 15 of them marked breaking_change from 2 to 29 October (12). 25+10+12+12+12+12 = 83.

Postiz API + MCP 88

OpenAPI 3.1.0 at docs.postiz.com/public-api/openapi.json with 27 paths, and zod input schemas on every MCP tool in source (25). llms.txt and Markdown versions of the docs pages (10). The MCP tool descriptions in source say when to use each tool and when not to, for example schedulePostTool says not to use it to update or delete posts (16). Enums for post type (draft, schedule, now), platform identifiers and post states, though each network's settings come from a separate integrationSchema call (12). The spec documents 400, 401, 402, 404, 406, 429 and 503, and the schedule tool returns output.errors naming what to fix (12). Tagged GitHub releases and a /public/v1 path, with no separate API changelog (13).

Score by category

CategoryWeightZernio (formerly Late) API + MCPPostiz API + MCPEdge
Reliability16%8043Zernio (formerly Late) API + MCP +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8388Postiz API + MCP +5
Agent ergonomics13%8865Zernio (formerly Late) API + MCP +23
Security & auth14%6549Zernio (formerly Late) API + MCP +16
Payments & pricing10%6045Zernio (formerly Late) API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8783Zernio (formerly Late) API + MCP +4
Transparency & trust7%7182Postiz API + MCP +11
Negative events≤15-5-15
TotalBB 71.5/100D 47.1/100

Facts side by side

FactZernio (formerly Late) API + MCPPostiz API + MCP
KindHTTP APIHTTP API
VendorZernioPostiz (Gitroom)
Hosted endpointhttps://zernio.com/api/v1https://api.postiz.com/public/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicencenoneAGPL-3.0
Tools exposednone13
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.zernio/zernionot listed
Last release2026-11-012026-10-24
Terms last updated2026-10-082026-05-03
Privacy policy last updated2026-10-082026-05-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity46k npm/wk, 44k PyPI/wk37k stars, 368 npm/wk
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Zernio (formerly Late) API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Zernio (formerly Late) API + MCP

Idempotency-Key on post creation and other writes, kept 24 hours, and a public DPA with a subprocessor list. Breaking changes keep shipping inside v1 on the day they're marked, 15 from 2 to 29 October 2026, while the changelog says they ship only as a new path version.

Postiz API + MCP

AGPL-3.0 and self-hostable with the API and MCP included, 34 platforms, with annotated MCP tools in the source. Postiz published 20 security advisories between March and October 2026, three of them Critical in late October, all fixed in releases. Create-post is capped at 90 requests an hour on every Cloud plan.

Before you call either

Zernio (formerly Late) API + MCP

  1. Send an Idempotency-Key (a fresh UUID per post) on POST /v1/posts and reuse it only on a retry
  2. Give timestamps an explicit offset, because times without one follow the profile timezone when it has one
  3. Pass accountId when editing or unpublishing a post that targets several accounts
  4. Wait Retry-After on 429. Analytics endpoints have their own per-second window
  5. Read the changelog's breaking_change entries before each deploy and pin the SDK version, because v1 changes without a new path

Postiz API + MCP

  1. Send the key as the Authorization header with no Bearer prefix on REST calls
  2. Batch several posts into one create request to stay under 90 an hour
  3. Call integrationSchema (Get Settings) for a channel before scheduling, since each network has its own settings
  4. Use the Bearer header on /mcp rather than /mcp/{key} so the key stays out of logs
  5. Run v2.25.3 or later when self-hosting, since earlier versions carry three Critical advisories published on 23 and 24 October 2026

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Zernio (formerly Late) API + MCP or Postiz API + MCP?

Zernio (formerly Late) API + MCP scores 71.5 (BB) on agent readiness against Postiz API + MCP's 47.1 (D), and leads in 5 of 7 scored categories. Postiz API + MCP leads on schema & documentation and transparency & trust.

Do Zernio (formerly Late) API + MCP and Postiz API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Zernio (formerly Late) API + MCP and Postiz API + MCP without installing anything?

Yes. Zernio (formerly Late) API + MCP has a hosted endpoint at https://zernio.com/api/v1 and Postiz API + MCP at https://api.postiz.com/public/v1.

Are Zernio (formerly Late) API + MCP and Postiz API + MCP open source?

No open-source release is listed for Zernio (formerly Late) API + MCP. Postiz API + MCP is open source (AGPL-3.0).

Other comparisons with Zernio (formerly Late) API + MCP or Postiz API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.