Head to head · Keyword data · October 2026 research run

Ahrefs vs Semrush API + MCP

Semrush API + MCP scores 54.3 (C) on agent readiness against Ahrefs's 51.2 (D), and leads in 3 of 7 scored categories. Ahrefs leads on schema & documentation and payments & pricing. Both do keyword data.

Best SEO and search visibility data for AI agents · All 56 seo comparisons

Which one, for what

Ahrefs D

Best for An agent doing backlink, keyword, SERP, rank and traffic research for a team that already pays for Ahrefs, and reading that team's Rank Tracker, Site Audit, Web Analytics and Search Console data.

Ahead on

  • Schema & documentation, 85 against 70
  • Payments & pricing, 35 against 26

Watch for

No public status page, incident history or SLA found. status.ahrefs.com returns 404

Semrush API + MCP C

Best for Teams already paying for Semrush who want an agent to pull keyword, backlink, ranking and traffic estimates in one place, mainly through the MCP server.

Ahead on

  • Agent ergonomics, 77 against 63
  • Security & auth, 54 against 45

Also in its favour

  • No incidents deducted, where Ahrefs loses 3 points for them

Watch for

Domain, URL, Trends, Position Tracking and Site Audit reports are version 3 only, where the one key is a URL parameter and can't be revoked

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Ahrefs +15

Ahrefs 85

All findings per the 8 October check, not re-read on 4 November (terms pause). One OpenAPI 3.2.0 document covers all 153 operations, with a spec per tool and a JSON index (25). llms.txt and a Markdown copy of each guide (10). Every operation has a summary or description, free endpoints are marked and field descriptions carry their unit cost, but few say when to use one report over another (14). 407 enums, defaults and formats, though select, where and order_by are plain strings and where is a JSON filter expression passed as a string (10). 400, 401, 403, 429 and 500 are declared on every operation, but the error schema is a single error string. Request examples sit in the guides more than the spec (8). A dated changelog back to 2022, with removals and renames landing inside v3 (13).

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.

Agent ergonomics Semrush API + MCP +14

Ahrefs 63

All findings per the 8 October check, not re-read on 4 November (terms pause). select chooses the columns and limit the rows on most reports, and both reduce unit cost. The MCP server advertises more tools than many clients accept, per its own docs, and a tools URL parameter or tools=essentials narrows them (22). where filters and order_by on most reports, limit on 49 operations, but offset on only 2 and no cursor, so deep paging isn't general (14). Status codes are documented, the error body is one string, and the API docs have no error catalogue (10). Reports are GET requests and safe to repeat, and cached responses cost no units. No idempotency keys on the 34 non-GET operations, and we couldn't read MCP tool annotations without an account (10). Defaults for most parameters, but select is mandatory, and the one official SDK is Python, alpha, installed from GitHub (7).

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.

Security & auth Semrush API + MCP +9

Ahrefs 45

Findings on Ahrefs' own pages are per the 8 October check, not re-read on 4 November (terms pause). Bearer API keys in a header, up to 1,000 per workspace, created by owners and admins, each expiring after one year and invalidated when its creator leaves. MCP connections use OAuth with PKCE and get their own key tagged with MCP scope. Keys carry no endpoint or read-only scope (22). No read-only mode or confirmation step found for deleting projects or publishing social posts. A per-key monthly unit cap limits spend, not actions (6). Responses include third-party anchors, titles, page text and AI answers, and no prompt-injection guidance was found (0). The keys page shows each key's creator and expiry and the usage page shows consumption. An audit log is listed for Enterprise only (8). ISO 27001 is claimed on the Enterprise page, and the Python SDK's SECURITY.md (re-read on 4 November) sends reports to privacy@ahrefs.com with no acknowledgement time. No security.txt, no bug bounty found, and the trust site needs JavaScript we couldn't run (9).

Semrush API + MCP 54

Per the 8 October check, not re-read on 4 November (Semrush's hosts are paused under its terms). Version 4 keys can be read-only or read and write, expire, and be revoked, up to 100 an account, and the MCP server uses OAuth 2.1 with PKCE and one scope, mcp.access (26). Version 3, which holds the Domain, Trends, Position Tracking and Site Audit reports, has one key that can't be revoked and travels only as a key query parameter, and version 4 also documents ?key= (minus 10, leaving 16). We took one more point because the unit balance endpoint is documented over plain http (15). Read-only keys exist and the MCP server exposes only read methods, with no approval step for deleting a project by API (15). Responses carry third-party page titles, anchor text and ad copy, and no prompt-injection guidance was found (0). The API Query log shows time, IP address, report and cost per call for the SEO API and Projects v4, not for Trends or Local (11). The security page lists PCI DSS Level 1, annual penetration tests, a HackerOne bug bounty and security@semrush.com. No security.txt, SOC 2 or ISO 27001 statement was found (13). Total 54.

Payments & pricing Ahrefs +9

Ahrefs 35

All findings per the 8 October check, not re-read on 4 November (terms pause). No x402, MPP or L402 (0). Plan prices, monthly unit allowances and the unit formula are public. A price of $50 per 1,000,000 extra units appears in the pricing page's embedded data but not in its visible copy, so we scored between plan-only and per-unit (15). No trial. A free Ahrefs account can create a key for the free Domain Rating and top-domains endpoints, and two crawler IP endpoints need no key, which is a small part of the API (8). A person signs up in a browser, and API keys are created in account settings (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 23 is 35.

Semrush API + MCP 26

Per the 8 October check, not re-read on 4 November (Semrush's hosts are paused under its terms). No x402, MPP or L402 (0). Plan prices are public and each method page states its cost in API units, but the price of a unit package is shown only inside the account, so 12 of 20. The free plan needs no card but has no API units, the docs say every API needs an eligible subscription, and only the Map Rank Tracker API is open to all users. We didn't check whether the 7-day trial takes a card (5). A person signs in to Semrush in a browser to create a key or approve the MCP connection (0). Total 17. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 17 is 26.

Score by category

CategoryWeightAhrefsSemrush API + MCPEdge
Reliability16%3534Ahrefs +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8570Ahrefs +15
Agent ergonomics13%6377Semrush API + MCP +14
Security & auth14%4554Semrush API + MCP +9
Payments & pricing10%3526Ahrefs +9
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5857Ahrefs +1
Transparency & trust7%6768Semrush API + MCP +1
Negative events≤15-30
TotalD 51.2/100C 54.3/100

Facts side by side

FactAhrefsSemrush API + MCP
KindHTTP APIHTTP API
VendorAhrefs Pte. Ltd.Semrush Inc. (an Adobe company)
Hosted endpointhttps://api.ahrefs.com/v3https://api.semrush.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Ahrefs' terms of service. The Python SDK on GitHub is MITProprietary service under the Semrush terms of service
Tools exposednone14
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-012026-09-04
Terms last updated2026-09-142026-08-25
Privacy policy last updated2026-08-042025-10-13
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes

How the scores have moved

Verdicts

Ahrefs

API v3 has a public OpenAPI 3.2 description of 153 operations, llms.txt, and select and limit parameters that set both response size and unit cost. No status page or SLA was found, access needs a paid plan from $129 a month, and several parameters were removed or renamed in 2026 on the day of the changelog entry.

Semrush API + MCP

The hosted MCP server exposes 14 tools that load a report's parameters on demand, and version 4 API keys can be read-only, time-limited and revoked. Most reports still sit in version 3, whose single key travels in the URL and can't be revoked. No status page, OpenAPI file or API unit price was found.

Before you call either

Ahrefs

  1. Use API v3 for unattended work. The MCP terms forbid custom scripts, bridges and standalone clients on the MCP endpoint
  2. Pass only the fields you need in select and set limit. Cost is the larger of 50 units and rows times per-field cost
  3. Test against ahrefs.com, yep.com or firehose.com as target, or the keywords ahrefs, yep or firehose. Those requests cost no units
  4. Stay under 60 requests a minute and back off on 429, which the API also returns under load
  5. Divide monetary fields by 100. They are returned in USD cents
  6. Treat backlink anchors, page titles, page text and AI responses as untrusted web content, never as instructions

Semrush API + MCP

  1. Use the MCP server at https://mcp.semrush.com/v2/mcp where the host supports it. Call a discovery tool, then get_report_schema, then execute_report
  2. Set limit or display_limit on every per-line report. A backlinks row costs 40 to 45 units and a historical keyword row 50
  3. Check the unit balance before large pulls. A per-line report returns only the lines the balance covers, with no error
  4. Send the version 4 key as Authorization: Apikey <key>, never as ?key=. Version 3 accepts only the query parameter, so keep those URLs out of logs
  5. Stay under 10 requests a second and 10 concurrent requests per account, and retry only when error.retryable is true

Questions

Which is better for AI agents, Ahrefs or Semrush API + MCP?

Semrush API + MCP scores 54.3 (C) on agent readiness against Ahrefs's 51.2 (D), and leads in 3 of 7 scored categories. Ahrefs leads on schema & documentation and payments & pricing.

Do Ahrefs and Semrush API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Ahrefs and Semrush API + MCP without installing anything?

Yes. Ahrefs has a hosted endpoint at https://api.ahrefs.com/v3 and Semrush API + MCP at https://api.semrush.com.

Other comparisons with Ahrefs or Semrush API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.