Semrush API + MCP vs SpyFu API

Semrush API + MCP 57

Per the 8 October check, not re-read on 4 November (hosts paused under the terms). The newest dated release note was 4 September 2026, for the Review Management reply endpoints, 61 days before this check (20). Three dated entries fall inside the 90 days from 6 August, on 19 August, 1 September and 4 September; the 15 July entry has left the window (20). A public changelog and a tech support form, with no public developer forum or issue tracker found (9). No official SDK. Semrush says its apps are in the Claude, ChatGPT and Perplexity directories (3). Doc pages carried update dates from August and September 2026 (5). Total 57.

SpyFu API 16

Closed service. No changelog. The newest dated docs change found is 13 July 2026 (the rate-limits and pricing pages' updatedAt), 116 days before this check (10). Reference pages are dated between August 2025 and 9 July 2026, so fewer than three dated changes in 90 days (0). A help centre and support email, with no public changelog or tracker (6 of 15). No official SDK (0). No package to judge (0). 10+0+6+0+0 = 16.

Semrush API + MCP 68

Per the 8 October check, not re-read on 4 November (Semrush's hosts are paused under its terms). Closed service with terms updated on 25 August 2026 (re-read on 4 November, unchanged) that include API clauses on rate, caching and AI use (15). A privacy policy, a DPA, a sub-processor list and AI terms that say Semrush doesn't train models on user input. Retention is stated as long as reasonably necessary, with deletion no sooner than 30 days after termination, and the privacy policy of 13 October 2025 doesn't mention Adobe (20). Release notes mark methods deprecated on dated entries but say only that they remain operational temporarily, with no removal date or notice policy (8). Nine sub-processors listed with countries and data centres stated as in the United States. The list names Equinix where the security page names Digital Realty (16). Total 59.

SpyFu API 38

Closed service under terms naming SpyFu, Inc., updated 25 February 2019, under Arizona law (15 of 30). The privacy policy carries no date, retention periods, controller or named processors, and says data is moved to the United States (5 of 30). No deprecation policy or notices found (0 of 20). No subprocessors named; data location is the United States (3 of 20). 15+5+0+3 = 23.

Semrush API + MCP 77

Per the 8 October check, not re-read on 4 November (Semrush's hosts are paused under its terms). The MCP server names 14 tools, 12 for discovery plus get_report_schema and execute_report, so a report's parameters load only when asked for. 15 for 11 to 30 tools plus 7 for that on-demand design (22). Version 4 has limit, offset, order_by, fields and a filter language, and version 3 has display_limit, display_offset, display_filter and export_columns (20). Version 4 errors carry a request id and a retryable flag, version 3 answers with text codes, and a per-line report returns fewer lines without an error when units run short (15). Report calls are reads and empty responses cost nothing, but no idempotency key was found for Projects or Local writes and MCP annotations weren't read (12). Few required parameters and sensible defaults, with no official SDK found (8). Total 77.

SpyFu API 65

Rows are billed, so page size controls cost; single or multiple rows per request by endpoint, and searchType selects analyses on one endpoint (18 of 25). Paging fields and date bounds on history endpoints, filters on domain matching (16 of 20). 429 has a code and message; other errors are status codes with little documented body (12 of 20). All GET reads, safe to retry (14 of 20). No official SDK found (5 of 15). 18+16+12+14+5 = 65.

Semrush API + MCP 34

Graded on the hosted lines for the REST APIs and the MCP server, per the 8 October check, not re-read on 4 November (Semrush's terms bar scraping its Services and related systems, so its hosts are paused). No public status page was found. None is linked from the developer docs, the home page or the security page, and status.semrush.com doesn't resolve, and on 4 November semrush.statuspage.io redirected to Statuspage's own home page (0). With no page there is no incident history to read (5). Limits are published as 10 requests a second and 10 simultaneous requests per account, with per-method limits for Listing Management (15). Version 4 documents 429 and an error.retryable flag, and version 3 lists ERROR 429, but no Retry-After header, backoff guidance or idempotency key for Projects and Local writes was found (6). The pricing page lists an Enterprise SLA without terms or a figure, and the security page cites only the infrastructure providers' 99.9 per cent target (2). Version 3 and the MCP server carry no preview label, but the version 4 Keyword and Backlinks reports the docs recommend for new work are marked Early Access (6). Total 34.

SpyFu API 45

Hosted lines. No status page found; status.spyfu.com did not resolve and the docs link none (0). No incident history to read (5). Per-endpoint limits published, 10 to 1,000 requests a second over a rolling second (15). 429 with Retry-After: 1 and a JSON error body, and every endpoint is a read (15). No SLA found (0). Generally available (10). 0+5+15+15+0+10 = 45.

Semrush API + MCP 70

Per the 8 October check, not re-read on 4 November (Semrush's hosts are paused under its terms). No OpenAPI or similar file was found on the developer site, and the guessed paths return 404. The MCP server's get_report_schema tool returns a report's parameters at run time, which we count as a partial contract we couldn't read without an account (8). llms.txt at the site root, for the API and for each version, though no Markdown twins of the pages (10). Each method page describes every parameter, and the API llms.txt says which API and version to pick for each task. MCP tool descriptions weren't read (14). Version 4 parameters state type, required status and allowed values such as country codes, scope and intent, while version 3 uses coded column names like Ph and Po with CSV output (10). Every method has a request example and a response sample, version 4 documents its error object and 11 status codes, and version 3 lists its numbered errors (13). Versions 3 and 4 are documented separately with dated release notes back to March 2026 (15). Total 70.

SpyFu API 75

Every reference page embeds an OpenAPI 3.1 definition with security schemes and responses, but no single downloadable file is linked (20 of 25). llms.txt and a Markdown twin of every page (10). Descriptions say what each endpoint returns and how it differs from its neighbours ('unlike term-based endpoints...') (17 of 20). Typed parameters with descriptions, examples and required flags (12 of 15). 200, 400, 401 and 500 in the definitions and a 429 example, little on error bodies (11 of 15). v2 in every path, but no changelog (/changelog answered 404) (5 of 15). 20+10+17+12+11+5 = 75.