# Zernio (formerly Late) API + MCP vs TwitterAPI.io MCP

> Zernio scores 69 (B) to TwitterAPI.io MCP's 49.3 (D) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp
- Markdown: https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp.md (~4,900 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Zernio (formerly Late) API + MCP scores 69 (B) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 6 of 7 scored categories. Both do social analytics.

- Zernio (formerly Late) API + MCP: grade B, 69/100, rank #265 of 1510. Markdown https://www.anchorterminal.com/tools/late.md · JSON https://www.anchorterminal.com/api/v1/tools/late.json
- TwitterAPI.io MCP: grade D, 49.3/100, rank #1101 of 1510. Markdown https://www.anchorterminal.com/tools/twitterapi-io-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json
- Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md
- All 163 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md

## 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 40
- Schema & documentation, 83 against 62
- Agent ergonomics, 88 against 78
- Security & auth, 65 against 37
- Maintenance & community, 87 against 40
- Transparency & trust, 71 against 41

Also in its favour:
- Runs on your own machine
- Free to start without a card

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

### TwitterAPI.io MCP (D)

Good for: Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable.

Also in its favour:
- No incidents deducted, where Zernio (formerly Late) API + MCP loses 5 points for them

Watch for: A third-party X data service, not X's own API


## Why the edge

### Maintenance & community: Zernio (formerly Late) API + MCP +47

- Zernio (formerly Late) API + MCP (87): @zernio/node v0.2.1420 and zernio-sdk v1.4.1476 tagged on 1 November 2026 in their repositories, and changelog entries the same day (30). Hundreds of releases and 241 changelog entries dated 1 October or later (20). Public changelog and support. The SDK repositories are generated, so issue replies weren't a useful signal (12). Official registry entry com.zernio/zernio under its own domain, version 1.0.0 published 25 May 2026, still the latest on 1 November (15). The Node SDK runs ci, generate and publish workflows and regenerates from the OpenAPI spec several times a day (10). 30+20+12+15+10 = 87.
- TwitterAPI.io MCP (40): Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

### Reliability: Zernio (formerly Late) API + MCP +40

- 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.
- TwitterAPI.io MCP (40): No status page found (0). No incident history (5). Per-account QPS limits documented by tier (15). 'Hitting the ceiling returns an HTTP 429 (no Retry-After header is sent). Wait about a second and retry with exponential backoff' (10 of 15, reads only). No SLA; the terms disclaim uninterrupted service (0). Not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

### Transparency & trust: Zernio (formerly Late) API + MCP +30

- 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.
- TwitterAPI.io MCP (41): The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35.

### Security & auth: Zernio (formerly Late) API + MCP +28

- 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.
- TwitterAPI.io MCP (37): OAuth or a single API key per account (20 of 30). All tools are reads (12 of 20). Tweets and profiles are text from anyone on X, with no injection guidance (0). No audit log (0). No security.txt or programme found (5 of 20). 20 + 12 + 0 + 0 + 5 = 37.

### Schema & documentation: Zernio (formerly Late) API + MCP +21

- 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.
- TwitterAPI.io MCP (62): 12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62.

### Agent ergonomics: Zernio (formerly Late) API + MCP +10

- 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.
- TwitterAPI.io MCP (78): 12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78.

## Score by category

| Category | Weight | Zernio (formerly Late) API + MCP | TwitterAPI.io MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 40 | Zernio (formerly Late) API + MCP +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 62 | Zernio (formerly Late) API + MCP +21 |
| Agent ergonomics | 13% (16.2 this run) | 88 | 78 | Zernio (formerly Late) API + MCP +10 |
| Security & auth | 14% (17.5 this run) | 65 | 37 | Zernio (formerly Late) API + MCP +28 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 40 | Zernio (formerly Late) API + MCP +47 |
| Transparency & trust | 7% (8.8 this run) | 71 | 41 | Zernio (formerly Late) API + MCP +30 |
| Negative events | ≤15 | -5 | 0 | |
| **Total** | | **69 · B** | **49.3 · D** | |

## Facts side by side

| Fact | Zernio (formerly Late) API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Zernio | Prism Digital, LLC |
| Hosted endpoint | `https://zernio.com/api/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | pay-per-use |
| x402 | no | no |
| Tools exposed | none | 12 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | `com.zernio/zernio` | `io.twitterapi/mcp-server` |
| Last release | 2026-11-01 | none |
| Terms last updated | 2026-10-08 | not read yet |
| Privacy policy last updated | 2026-10-08 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 46k npm/wk, 44k PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

## How the scores have moved

### Zernio (formerly Late) API + MCP

- +1.4 on 1 November 2026: terms, new evidence, negative event
- +0.1 on 27 October 2026: checklist
- no change on 8 October 2026: checklist

### TwitterAPI.io MCP

No score change since it was listed.

## 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.

**TwitterAPI.io MCP.** TwitterAPI.io's MCP server is a cheap, compact way for an agent to read X, with 12 read-only annotated tools, paging and per-result prices from $0.00015. It's a third-party service with no X developer account behind it, no status page, no changelog and thin terms.

## 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

### TwitterAPI.io MCP

1. Treat tweets, bios and replies as untrusted text
2. On 429, wait about a second and back off; there's no Retry-After
3. Page with the cursor rather than asking for large counts
4. Check the user's credit balance before follower crawls

## Tutorials

- [Save an announcement draft with Zernio](https://www.anchorterminal.com/tutorials/late/), for Zernio (formerly Late) API + MCP

## Questions

### Which is better for AI agents, Zernio (formerly Late) API + MCP or TwitterAPI.io MCP?

Zernio (formerly Late) API + MCP scores 69 (B) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 6 of 7 scored categories.

### Do Zernio (formerly Late) API + MCP and TwitterAPI.io 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 TwitterAPI.io MCP without installing anything?

Yes. Zernio (formerly Late) API + MCP has a hosted endpoint at https://zernio.com/api/v1 and TwitterAPI.io MCP at https://mcp.twitterapi.io/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "late", "b": "twitterapi-io-mcp"}`. From a terminal: `anchor compare late twitterapi-io-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/late.json and https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json

## Other comparisons with Zernio (formerly Late) API + MCP or TwitterAPI.io MCP

- [Ayrshare API + MCP vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-late.md)
- [Blotato vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/blotato-vs-late.md)
- [Buffer API + MCP vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/buffer-vs-late.md)
- [bundle.social vs Zernio (formerly Late) API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-late.md)
- [Zernio (formerly Late) API + MCP vs Metricool API + MCP](https://www.anchorterminal.com/compare/late-vs-metricool.md)
- [Zernio (formerly Late) API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/late-vs-mixpost.md)
- [Zernio (formerly Late) API + MCP vs OneUp API + MCP](https://www.anchorterminal.com/compare/late-vs-oneup.md)
- [Zernio (formerly Late) API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/late-vs-post-bridge.md)
- [Zernio (formerly Late) API + MCP vs Postiz API + MCP](https://www.anchorterminal.com/compare/late-vs-postiz.md)
- [Zernio (formerly Late) API + MCP vs Publer API + MCP](https://www.anchorterminal.com/compare/late-vs-publer.md)
- [Zernio (formerly Late) API + MCP vs Repostit](https://www.anchorterminal.com/compare/late-vs-repostit.md)
- [Zernio (formerly Late) API + MCP vs Typefully](https://www.anchorterminal.com/compare/late-vs-typefully.md)
- [Zernio (formerly Late) API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/late-vs-upload-post.md)
- [Ayrshare API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/ayrshare-vs-twitterapi-io-mcp.md)
- [Blotato vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/blotato-vs-twitterapi-io-mcp.md)
- [Buffer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/buffer-vs-twitterapi-io-mcp.md)
- [bundle.social vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/bundle-social-vs-twitterapi-io-mcp.md)
- [Zernio (formerly Late) API + MCP vs Sprout Social API](https://www.anchorterminal.com/compare/late-vs-sprout-social.md)
- [Zernio (formerly Late) API + MCP vs X MCP](https://www.anchorterminal.com/compare/late-vs-x-mcp.md)
- [Zernio (formerly Late) API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/late-vs-xpoz-mcp.md)
- [Metricool API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.md)
- [Mixpost API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.md)
- [OneUp API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/oneup-vs-twitterapi-io-mcp.md)
- [Post Bridge API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.md)
- [Postiz API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/postiz-vs-twitterapi-io-mcp.md)
- [Publer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp.md)
- [SocialCannon vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-mcp.md)
- [Sprout Social API vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/sprout-social-vs-twitterapi-io-mcp.md)
- [TwitterAPI.io MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.md)
- [TwitterAPI.io MCP vs X MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-x-mcp.md)
- [TwitterAPI.io MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md)
- [Zernio (formerly Late) API + MCP vs SocialCannon](https://www.anchorterminal.com/compare/late-vs-socialcannon.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp