Pricing, limits, and integration
RobotSpeed's 12 free MCP SEO tools are usable without a paid plan, while the 27 pro MCP tools and the account-level API sit behind your subscription and OAuth. The REST API authenticates with rs_ keys in an X-API-Key header, and rate limits are documented with higher ceilings for authenticated requests.
The paid product is billed per site by monthly credits (€109 to €659 a month) rather than per API call, so the API and MCP are integration surfaces on top of your plan, not separately metered products. Confirm the current rate limits in the docs before a high-volume build.
How much does the RobotSpeed API actually cost?
RobotSpeed 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
Which AI clients can read RobotSpeed data?
Not every AI assistant supports MCP natively. Here's the per-client picture for RobotSpeed specifically.
| Client | Support | Notes |
|---|---|---|
| Claude Code | Native MCP | Documented one-line setup: claude mcp add --transport http robot-speed https://www.robot-speed.com/api/mcp. |
| Claude (Desktop/Web) | Native MCP | Add via Connectors and authenticate with OAuth for the pro tools. |
| Cursor | Native MCP | Documented JSON config to add the MCP server URL. |
| n8n | Native MCP | Native n8n integration alongside Zapier and Make, plus webhooks for article events. |
RobotSpeed also has an MCP server
If you're wiring RobotSpeed into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See RobotSpeed MCP pageWhat you can build with the RobotSpeed API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue RobotSpeed 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 RobotSpeed reporting at scale
- White-label RobotSpeed data into client-branded dashboards
- Run scheduled multi-account reports without logging into the RobotSpeed UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for RobotSpeed
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for RobotSpeed 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 RobotSpeed events in real time instead of polling.
- 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.
- No-code fallback: Zapier and Make.com cover the common triggers if you want to skip writing API code for simple flows.
Agent-readiness verdict
A real, documented REST API with rs_ keys, an X-API-Key header, multi-language code examples and event webhooks. The public surface is currently focused on articles rather than the whole platform, which holds it to a 7 out of 10, but it is well ahead of most content autopilots.
RobotSpeed API FAQ
Does RobotSpeed support webhooks?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Does RobotSpeed have a public API?+
Sources
- RobotSpeed official site: https://www.robot-speed.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.