Pricing, limits, and integration
API and MCP access come bundled with the SaaS subscription rather than sold as a separate product, and both are absent entirely from the $50/mo Individual plan. They switch on at the $100/mo Team plan (200,000 API credits/month), scale to Team x2 at $169/mo (400,000 credits/month), and top out at Agency for $410/mo (2,000,000 credits/month, 10 requests/second versus 1/second on the lower tiers).
There is no separate metered API price list outside the SaaS plan tiers; usage is governed by the credit allotment and request-per-second cap that comes with your subscription. Authentication for both the REST API and the MCP server uses the same SERPSTAT_API_TOKEN.
For agent-driven use, the MCP server is the faster path since it surfaces the full 65-tool catalogue with category filtering built in. Budget for the $100/mo Team plan minimum if API or MCP access is the reason you are evaluating Serpstat, since the $50/mo entry tier includes neither.
How much does the Serpstat API actually cost?
Serpstat's v4 REST API is tier-gated: absent on Individual ($50/mo), unlocked from Team ($100/mo) up.
- Individual ($50/mo) has no API access at all. Team ($100/mo) is the cheapest plan with it, at 200,000 API credits/month and 1 request/second.
- Team x2 ($169/mo): 400,000 credits/month, same 1 request/second cap. Agency ($410/mo): 2,000,000 credits/month, 10 requests/second.
- Covers Search Analytics, Backlinks, Rank Tracking, and Site Audit endpoints. No separate metered price list outside the plan tiers.
API at a glance
Which AI clients can read Serpstat data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Serpstat specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Explicitly documented in the official MCP server's README, including a ready-to-paste config block. Requires SERPSTAT_API_TOKEN and a Team-plan-or-higher subscription. |
| Claude Code | Native MCP | Works via the same official MCP server (stdio, npx @serpstat/serpstat-mcp-server) with SERPSTAT_API_TOKEN configured. |
| Cursor | API-only (custom code) | Not explicitly listed as a supported client in the official README (Claude Desktop and Gemini CLI are named), though the server should work with any MCP-compatible client. Verify locally before relying on it; the v4 REST API is the documented fallback. |
| n8n | API-only (custom code) | Drive via the credit-metered v4 REST API. Requires SERPSTAT_API_TOKEN and at least the Team plan. |
Serpstat also has an MCP server
If you're wiring Serpstat into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Serpstat MCP pageWhat you can build with the Serpstat API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Serpstat into your daily workflow
- Pull a digest of ranking changes into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Serpstat reporting at scale
- White-label Serpstat data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Serpstat UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Serpstat
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Serpstat data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Serpstat API docs: https://api-docs.serpstat.com/docs/serpstat-public-api/jenasqbwtxdlr-introduction-to-serpstat-api curl -X GET "https://api-docs.serpstat.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 api-docs.serpstat.com/docs/serpstat-public-api/jenasqbwtxdlr-introduction-to-serpstat-api.
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
A credit-metered v4 REST API covering the platform's core data (search analytics, backlinks, rank tracking, site audit), gated to the Team plan ($100/mo) and up. Solid coverage and documentation, docked slightly for being absent on the entry tier and for a 1 request/second cap below Agency. An 8 out of 10 for API agent-readiness.
Moderate agent-fit with official MCP support. Serpstat offers an official MCP server and documented public API with dual auth options, making it accessible for Claude workflows. Missing OpenAPI specs and SDKs limits programmatic flexibility compared to agent-native tools.
Serpstat API FAQ
Does Serpstat have a public API?+
What auth does the Serpstat API use?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Serpstat official site: https://serpstat.com
- API docs: https://api-docs.serpstat.com/docs/serpstat-public-api/jenasqbwtxdlr-introduction-to-serpstat-api
- MCP server: https://github.com/SerpstatGlobal/serpstat-mcp-server-js
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.