# Zernio (formerly Late) API + MCP vs Xpoz MCP (slim)

> Zernio scores 69 (B) to Xpoz MCP's 39.6 (E) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/late-vs-xpoz-mcp.md (~4,700 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/late-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/late-vs-xpoz-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Zernio (formerly Late) API + MCP scores 69 (B) on agent readiness against Xpoz MCP's 39.6 (E), and leads in every scored category. Both do social analytics.

- Zernio (formerly Late) API + MCP: B 69, rank #265 of 1510 · https://www.anchorterminal.com/tools/late.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-mcp.min.md
- Zernio (formerly Late) API + MCP, 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 20; Schema & documentation, 83 against 64; Agent ergonomics, 88 against 63; Security & auth, 65 against 37; Payments & pricing, 40 against 30; Maintenance & community, 87 against 25; Transparency & trust, 71 against 29. Also Runs on your own machine; Free to start without a card.
- Xpoz MCP, good for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable. Also No incidents deducted, where Zernio (formerly Late) API + MCP loses 5 points for them.

| Category | Zernio (formerly Late) API + MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 80 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 64 |
| Agent ergonomics (13%) | 88 | 63 |
| Security & auth (14%) | 65 | 37 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 87 | 25 |
| Transparency & trust (7%) | 71 | 29 |

| Fact (where they differ) | Zernio (formerly Late) API + MCP | Xpoz MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Zernio | XPOZ |
| Hosted endpoint | `https://zernio.com/api/v1` | `https://mcp.xpoz.ai/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | API key |
| Tools exposed | none | 52 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `com.zernio/zernio` | `ai.xpoz/social-insights` |
| Last release | 2026-11-01 | none |
| Terms last updated | 2026-10-08 | not read yet |
| Privacy policy last updated | 2026-10-08 | no document linked |
| 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 |

Why the edge:
- Maintenance & community, Zernio (formerly Late) API + MCP +62: 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.); Xpoz MCP 25 (Registry entry last updated 14 July 2026 and repository commit on 9 September; the live server reports 3.0.0 (10). No dated releases in 90 days (0). Issues not read (0). Official registry entry ai.xpoz/social-insights (15). Docker packaging only (0). 10 + 0 + 0 + 15 + 0 = 25. 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 +60: 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.); Xpoz MCP 20 (No status page found (0). No history (5). Credit allowances, no rate limits found (5 of 15). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 5 + 0 + 0 + 10 = 20.)
- Transparency & trust, Zernio (formerly Late) API + MCP +42: 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.); Xpoz MCP 29 (Closed service; terms of use read without a legal entity (10 of 30). Data handling not read (5 of 30). No deprecation policy (0). Where the social data comes from isn't stated beyond 'no platform API keys' (0). 10 + 5 + 0 + 0 = 15.)
- 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.); Xpoz MCP 37 (One API key (20 of 30). 49 of 52 tools read-only (15 of 20). Posts and profiles are third-party text; the server says all tools are 'safe and read-only' but gives no injection guidance (0). No audit log (0). No security programme found (2 of 20). 20 + 15 + 0 + 0 + 2 = 37.)
- Agent ergonomics, Zernio (formerly Late) API + MCP +25: 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.); Xpoz MCP 63 (52 tools totalling about 238 KB (5). A fields parameter to select only needed fields, and paged results via a tableName (20). No documented errors (3 of 20). All annotated, 49 read-only (20). SDKs and a CLI (15). 5 + 20 + 3 + 20 + 15 = 63.)
- Schema & documentation, Zernio (formerly Late) API + MCP +19: 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.); Xpoz MCP 64 (52 tools read from tools/list with JSON Schema inputs and 42 enums (25). No llms.txt read (0). Server instructions explain paging and field selection (16 of 20). Typed inputs with enums (15). Examples on the home page (5 of 15). Registry 1.4.1 from July, server 3.0.0; no changelog (3 of 15). 25 + 0 + 16 + 15 + 5 + 3 = 64.)