Get an audit

Head to head · Social post · October 2026 research run

Zernio (formerly Late) API + MCP vs Typefully

Zernio (formerly Late) API + MCP scores 67.5 (B) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories. Typefully leads on transparency & trust. Both do social post.

Zernio (formerly Late) API + MCPZernio · HTTP API B67.5/100#232 of 841 TypefullyTypefully Inc. · HTTP API D49.1/100#713 of 841

Which one, for what

Zernio (formerly Late) API + MCP B

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

Ahead on

  • Reliability, 80 against 27
  • Agent ergonomics, 88 against 62
  • Security & auth, 57 against 38
  • Payments & pricing, 40 against 30
  • Maintenance & community, 87 against 82

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Several breaking changes shipped between 29 September and 1 October 2026 with no notice period

Typefully D

Good for An agent that drafts and schedules posts for one person's or one team's own accounts, with a human reviewing drafts and comments in the Typefully editor.

Ahead on

  • Transparency & trust, 64 against 58

Watch for

Rate limits are described by response headers only. No request numbers are published, and no Retry-After header is documented

Score by category

CategoryWeight this runZernio (formerly Late) API + MCPTypefullyEdge
Reliability16%208027Zernio (formerly Late) API + MCP +53
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28383even
Agent ergonomics13%16.28862Zernio (formerly Late) API + MCP +26
Security & auth14%17.55738Zernio (formerly Late) API + MCP +19
Payments & pricing10%12.54030Zernio (formerly Late) API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88782Zernio (formerly Late) API + MCP +5
Transparency & trust7%8.85864Typefully +6
Negative events≤15-4-3
Total67.5 · B49.1 · D

Facts side by side

FactZernio (formerly Late) API + MCPTypefully
KindHTTP APIHTTP API
VendorZernioTypefully Inc.
Hosted endpointhttps://zernio.com/api/v1https://api.typefully.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under Typefully's Terms of Service. The Agent Skill and its CLI script in typefully/agent-skills are MIT
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.zernio/zerniocom.typefully/mcp
Last release2026-10-012026-10-01
Terms last updated2026-10-082026-02-23
Privacy policy last updated2026-10-08no date given
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 textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity46k npm/wk, 44k PyPI/wknone
Agent reviews4/5 (2)none

Verdicts

Zernio (formerly Late) API + MCP

Idempotency-Key on post creation and other writes, kept 24 hours, with an Idempotent-Replayed header on replays. Several breaking changes shipped between 29 September and 1 October 2026 with no notice period.

Typefully

A public OpenAPI 3.1 document, Markdown docs and a hosted MCP server with OAuth cover drafts, scheduling, media and review comments, and planned drafts never publish until confirmed. Rate limits carry no published numbers, there is no status page or idempotency key, and both OAuth and API keys grant full access.

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 now follow the profile timezone rather than UTC
  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. Call https://zernio.com/api/v1, not the old getlate.dev base, and pin the SDK version

Typefully

  1. Call GET /v2/social-sets first. Every draft, media, tag and queue path needs a social_set_id
  2. Use plan_at or omit both dates to leave a draft unpublished. publish_at: "now" posts at once and is asynchronous
  3. Do not retry a failed publish blindly. Read the draft's status and publish_state first, because no idempotency key exists
  4. Read X-RateLimit-User-Remaining and X-RateLimit-SocialSet-Remaining on each response, and wait until the Reset timestamp after a 429
  5. Send the key only as Authorization: Bearer. The legacy MCP URL with ?TYPEFULLY_API_KEY= still works and puts the key in logs

Questions

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

Zernio (formerly Late) API + MCP scores 67.5 (B) on agent readiness against Typefully's 49.1 (D), and leads in 5 of 7 scored categories. Typefully leads on transparency & trust.

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

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

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

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

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

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.

Get an auditSee a sample report