Pricing, limits, and integration
Zernio's API and MCP server are the product, so access is included with the account rather than sold as a separate tier. Pricing is pay-per-connected-account: the first 2 accounts are free, then it is graduated ($6/month per account for accounts 3-10, $3/month for 11-100, and $1/month for 101-2,000), with enterprise pricing above 2,000 accounts. Every feature, including the API and MCP server, is available at every tier.
Two cost details matter for an agent build. X/Twitter API costs are passed through at exact platform rates, because Twitter charges per API call, while all other platforms are fully included. And WhatsApp requires a $2/month dedicated number if you want business messaging. So the variable parts of your bill are your account count, any X/Twitter call volume, and whether you provision a WhatsApp number.
Rate limits are tiered by plan: 60 requests per minute on the free tier, 600 on paid, and 1,200 on enterprise, with unlimited posting volume per connected account. For an agent that batches scheduling or polls analytics, the paid tier's 600 req/min is the practical floor. There are no official SDKs, so generate a client from the OpenAPI 3.1 spec, and use the hosted MCP server when you want an agent to drive Zernio directly rather than through your own code.
How much does the Zernio API actually cost?
Zernio publishes an API, but per-tier gating wasn't extracted automatically.
- Most likely scenario: API access is either included in all paid plans, or it's gated to higher tiers and we need to verify on the live docs page.
- Until verified, treat the question "which plan unlocks the API" as open. Don't budget on the assumption it's free with the cheapest paid plan.
Zernio API is sold as a standalone product with its own pricing — not bundled into a parent SaaS subscription. See the pricing details below and confirm current rates on the official API page.
API at a glance
Which AI clients can read Zernio data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Zernio specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect to the hosted MCP server at mcp.zernio.com/mcp; no custom integration needed. |
| Claude Code | Native MCP | Add the hosted MCP server; full publishing, analytics and inbox tools available to the agent. |
| Cursor | Native MCP | Native MCP support; add the Zernio server URL. |
| ChatGPT | Native MCP | Works as an MCP client against the hosted Zernio server. |
| n8n | API-only (custom code) | No native node; integrate via the REST API at /api/v1 with a Bearer token. |
Zernio also has an MCP server
If you're wiring Zernio into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Zernio MCP pageWhat you can build with the Zernio API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Zernio into your daily workflow
- Pull a digest of fresh activity into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Zernio reporting at scale
- White-label Zernio data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Zernio UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Zernio
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Zernio data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Zernio API docs: https://docs.zernio.com curl -X GET "https://api.zernio.com/<your-endpoint>" \ -H "Authorization: Bearer $TOKEN" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from docs.zernio.com.
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
Agent-readiness verdict
One of the strongest APIs in the social category, because the API is the product, not an afterthought. A clean REST surface at /api/v1, Bearer-token auth, an OpenAPI 3.1 spec, an llms.txt, and full coverage of publishing, ads, analytics and inbox across 15+ platforms. The only gaps are no official SDKs (you generate from OpenAPI) and webhooks that are referenced but not formally documented. A strong 9 out of 10.
Moderate agent fit with a working foundation. Zernio has an official MCP server and documented public API, which covers the basics for Claude/Cursor integration. The lack of OpenAPI specs, SDKs, and structured outputs makes deeper automation workflows harder to build and maintain.
Zernio API FAQ
Does Zernio have a public API?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Zernio official site: https://zernio.com
- API docs: https://docs.zernio.com
- MCP server: https://mcp.zernio.com/mcp
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.