Pricing, limits, and integration
Tidio's REST API and developer resources are included with the subscription rather than sold separately, and REST access starts on the free plan. The product itself is metered on billable conversations and, separately, on Lyro AI conversations, so programmatic activity that drives conversations consumes those allowances.
Authentication uses Tidio's API keys from the account settings, against an OpenAPI-documented surface covering conversations, contacts, tickets and Lyro data sources. Webhooks, which deliver events to your systems, are reserved for the Plus tier ($749/month).
For agent use, the practical path is the REST API for reads and writes, plus Lyro's own MCP and JS-action integrations for letting the agent call your tools mid-conversation. There is no MCP server to drive Tidio itself, so an external agent manages Tidio through the REST API rather than over MCP.
How much does the Tidio API actually cost?
Tidio 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.
API at a glance
Webhooks: Webhooks are supported but gated to the Plus tier ($749/month). They push events to your own systems for data sync, ticket creation and notifications.
Which AI clients can read Tidio data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Tidio specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Not supported | No Tidio MCP server to connect to; Lyro consumes MCP tools rather than exposing one. |
| Cursor | Not supported | No platform MCP server; integrate via the REST API instead. |
| n8n | API-only (custom code) | Integrate via the REST API (every plan) and webhooks (Plus tier). |
What you can build with the Tidio API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Tidio 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 Tidio reporting at scale
- White-label Tidio data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Tidio UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Tidio
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Tidio data older than the dashboard exposes
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- Webhooks available — react to Tidio events in real time instead of polling.
- Official SDKs: JavaScript. Use them to skip auth boilerplate and get type safety.
- 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
A developer-friendly REST API with OpenAPI docs, available even on the free plan, covering conversations, contacts, tickets and Lyro data sources. The one real limit is that webhooks are reserved for the $749 Plus tier. A fair 6 out of 10 for API agent-readiness.
Tidio API FAQ
Does Tidio have official SDKs?+
Does Tidio support webhooks?+
Does Tidio have a public API?+
Sources
- Tidio official site: https://www.tidio.com
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.