Head to head · Keyword data · October 2026 research run

Moz API vs Similarweb

Similarweb and Moz API score within a point of each other on agent readiness, 47.4 (D) and 46.7 (D). Moz API leads on reliability, agent ergonomics and payments & pricing. Both do keyword data.

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

Which one, for what

Moz API D

Best for Agents that need Domain Authority, backlink lists, link intersects, keyword volume and difficulty, search intent and ranking keywords at a low entry price, on a read-only data set.

Ahead on

  • Reliability, 42 against 35
  • Agent ergonomics, 74 against 67
  • Payments & pricing, 30 against 8

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.8 out of 5

Watch for

No working public status page was found, and moz.statuspage.io reports the Moz Status page as inactive

Similarweb D

Best for Traffic and engagement estimates, traffic channel mix and keyword click data for domains an agent doesn't own, with app, company and retail data on the same key.

Ahead on

  • Schema & documentation, 63 against 50
  • Security & auth, 52 against 38
  • Maintenance & community, 43 against 28

Watch for

API and MCP access need a Business, Enterprise or API-only plan bought through sales. The FAQ says there's no API test without a subscription

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.

Payments & pricing Moz API +22

Moz API 30

No x402, MPP or L402 (0). Plan prices, monthly rows and per-row overage prices are public without a login, re-read 5 November, and each method page states its row cost (20). The free plan of 50 rows a month requires a valid credit card, per the getting-started guide, so it doesn't count (0). A person has to sign up and check out in a browser before a token exists. The MCP server's OAuth has dynamic client registration but still needs the account owner to sign in (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Similarweb 8

Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. No x402, MPP or L402 found (0). No price per credit or API plan price is public. The credit cost per endpoint and the formula are published, which earns 5 of 20 as a departure from the checklist. No free tier or API trial, since the FAQ requires an active subscription (0). A person has to buy through sales and an admin has to create the key (0). Total 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Maintenance & community Similarweb +15

Moz API 28

The newest dated Moz API entry in the product updates archive is the MCP server beta of 14 August 2026, 83 days before this check (20). That is the only Moz API entry in the last 90 days. The 22 and 28 October entries cover Moz AI Explorer and Moz Data in Profound, which record no API change, and a webhooks guide for Moz Local Enterprise carries no date (0). A dated archive exists, and support is by api@moz.com and the help team contact form, with 24/7 online support claimed on the product page. We could not test response times, and the contact page returned 403 to our reader on 8 October (8). No official SDK was found (0). No packages to assess (0). 20 + 0 + 8 + 0 + 0 = 28.

Similarweb 43

Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. The newest dated API change on record is the deprecation of the legacy REST endpoints on 6 October 2026, in the migration guide, 30 days before 5 November and so within 30 days (30). The V5 docs' 24 September publish date records no change and no longer counts. Three dated entries in 90 days not established, because the V5 changelog didn't load (0). Two public changelogs and a help centre with ticket support (8 of 15). No official SDKs, and no registry entry we could read (0). The hosted MCP server and both docs sites were live and current (5 of 10). Total 43.

Security & auth Similarweb +14

Moz API 38

Plain revocable tokens, up to five per account, sent in the x-moz-token header and never in a URL. No scopes were found. The beta MCP server adds OAuth with PKCE and dynamic client registration, with a single scope named mcp (20). The Data methods only read, but there's no read-only or per-product token, and the MCP guide says the same token works on the Local endpoint, whose methods create, update, cancel and close locations (8). Results carry page titles, anchor text and search result snippets from the open web, and no prompt-injection guidance was found (0). Each response reports the quota used and the dashboard has a usage page behind a login we couldn't read. No audit log was found in the docs (5). security.txt gives a contact address, but on 5 November it carried Expiration: 2026-11-04T15:27:33-08:00, about three hours before our read, as on 8 October, and its policy page still returns 404. No SOC 2 or ISO 27001 statement and no bug bounty were found (5). 20 + 8 + 0 + 5 + 5 = 38.

Similarweb 52

Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. Revocable API keys created by admins, with up to 3 per user, no expiry and credit caps per user, plus OAuth with PKCE and a read scope on the MCP server (22 of 30). Less 10 because the capabilities endpoint documents the key in a ?api_key= query string. Data access is read-only and follows the plan's data sets and countries (14 of 20). No guidance found on untrusted content in returned URLs, keywords and app details (8 of 15). The keys table shows last use and monthly usage per key, and a credit dashboard shows usage by user (8 of 15). SOC 2 Type II and ISO 27001 stated, no security.txt, and the trust centre refused our reader (10 of 20). Total 52.

Schema & documentation Similarweb +13

Moz API 50

No downloadable OpenAPI or OpenRPC file is linked from the docs. Each method page carries its payload, result and quota definitions as JSON Schema inside the page itself, drawn into the rendered reference, which we count as a partial contract (8, a judgement call). moz.com/llms.txt returns 404 and no Markdown docs for agents were found (0). Method descriptions state the purpose and the row cost, and the guides explain async calls, errors and the new webhooks, but few say when not to use a method (10). Inputs are typed with enums for scope, sort, filters, engine and device, numeric ranges and required fields, per the 8 October check (13). Request and response examples appear on each method page and in cURL, Python and JavaScript, and the error guide lists 13 codes with sample bodies (14). The docs say the API is not versioned, and the product updates archive holds one dated Moz API entry in the last 90 days, the MCP beta of 14 August (5). 8 + 0 + 10 + 13 + 14 + 5 = 50.

Similarweb 63

Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. No public OpenAPI file found. Reference pages carry structured parameter and response definitions in Markdown, and the MCP tool schemas need a key to read (8 of 25). llms.txt on both docs sites with Markdown pages (10). Endpoint pages state purpose, output fields, constraints and credit cost, with little on when not to use one (12 of 20). Parameters are typed with enums for granularity and device, and defaults are stated (12 of 15). Request and response examples exist, and the error table has mismatched descriptions for codes 101 and 102 (9 of 15). Versioned paths and two changelogs, the newer one unreadable to us (12 of 15). Total 63.

Reliability Moz API +7

Moz API 42

Graded on the public JSON-RPC API with the hosted lines. No working public status page was found. moz.statuspage.io still redirects to a page saying Moz Status is inactive (5 November), the docs and help hub link none, and status.moz.com did not connect from our network (0). No readable incident history (5). Edge limits are published with numbers, 2,000 requests in 60 seconds, 20 client errors in 60 seconds and a 30-minute block after ten 401 or 403 responses in five minutes, plus one request every ten seconds on the free plan (15). Per-method 429 responses carry Retry-After and the docs say to honour it, edge 429 responses carry none and the docs ask for exponential backoff, server errors are said to be safe to retry with backoff, and no idempotency guidance was found for the Local write methods (12). The General Conditions promise commercially reasonable efforts at availability with no SLA or credits (0). The JSON-RPC API is generally available, and the MCP server is still beta (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.

Similarweb 35

Graded as a hosted service, on the V5 REST API and the hosted MCP server. No public status page found. similarweb.statuspage.io still redirects to a Statuspage Google sign-in on 5 November (0). No readable incident history (5). Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. Rate limits published, 10 requests a second for REST and 20 pending requests for Batch (15). 429 is documented with advice to add a rate limiter and errors aren't charged, but no Retry-After or backoff guidance was found, and Batch has a retry endpoint (5 of 15). The SLA page is dated January 2016 and its PDF returns 404 (0). V5 is announced as live and carries no beta label (10). Total 35.

Agent ergonomics Moz API +7

Moz API 74

List methods take limit (1 to 50 on link lists) and separate methods return a single keyword metric, but no field selection was found, and a site metrics object carries about 60 fields (15). Paging by opaque token, sort keys and named filters such as external, follow and gained_last_60_days (20). Errors carry a stable code, HTTP status, data.issue, data.key and an explanation, though the status field is named status in some bodies and httpStatus in others (19). The Data methods are reads, validation and quota checks run before any rows are used, and async calls can be polled again, but no idempotency keys were found for the Local write methods (13). site_query is the only required input on most site methods, the request id must be at least 24 characters, and no official SDK was found in the reviewed documentation (7). 15 + 20 + 19 + 13 + 7 = 74.

Similarweb 67

Per the 8 October check, not re-read on 5 November, since Similarweb's terms bar robots, spiders, scrapers and other automated means on its Site, Platform and Applications. V5 requests name the metrics wanted and take limit, so responses can be sized. The MCP tool count couldn't be read without a key, and the vendor cites more than 75 endpoints (15 of 25). limit, offset, sort and asc plus country, date and granularity filters (20). Errors are a short documented table with error_code and error_message in responses, and 401 is used for data not found (10 of 20). The data endpoints are reads, so retries are safe, and the MCP scope is read. Tool annotations unverified (14 of 20). Only domain is required on the endpoints read, and no SDKs exist (8 of 15). Total 67.

Score by category

CategoryWeightMoz APISimilarwebEdge
Reliability16%4235Moz API +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5063Similarweb +13
Agent ergonomics13%7467Moz API +7
Security & auth14%3852Similarweb +14
Payments & pricing10%308Moz API +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2843Similarweb +15
Transparency & trust7%6062Similarweb +2
Negative events≤1500
TotalD 46.7/100D 47.4/100

Facts side by side

FactMoz APISimilarweb
KindHTTP APIHTTP API
VendorSEOmoz, Inc.Similarweb Ltd.
Hosted endpointhttps://api.moz.com/jsonrpchttps://api.similarweb.com
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceProprietary service under the Moz API General Conditions (effective 12 August 2026 for new subscribers). Displaying Moz data to others requires attribution under the API legal pageProprietary service under Similarweb's terms of use
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-142026-09-24
Terms last updated2026-08-122025-03-19
Privacy policy last updated2025-04-082026-06-30
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews3.5/5 (4)2.8/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Moz API

The JSON-RPC API documents every error code, its rate limits and the row cost of each method, and failed validation uses no quota. No working status page, SLA, machine-readable spec or official SDK was found. Tokens carry no scopes, and the free plan needs a credit card.

Similarweb

The V5 API returns traffic estimates, keyword clicks and SERP positions with selectable metrics, and the hosted MCP server accepts OAuth with a read scope. Access needs a Business, Enterprise or API-only subscription sold through sales, with no API trial, public price per credit or public status page found.

Before you call either

Moz API

  1. Send a request id of at least 24 characters (letters, numbers and hyphens). A UUID works. Shorter ids are rejected with -32654.
  2. Stop on a 401. Ten 401 or 403 responses in five minutes block the caller for 30 minutes.
  3. On 429 with code -32658 wait the Retry-After seconds. On code -32650 no wait time is given, so back off exponentially.
  4. Call quota.lookup (free) before large pulls. List methods charge one row per result, and limit is capped at 50 on link lists.
  5. Poll async.call.lookup for data.keyword.serp.generate, and collect the result within 20 seconds of first seeing it complete.

Similarweb

  1. Send the key in the api-key header. The capabilities endpoint documents ?api_key= in the URL, which puts the secret in logs
  2. Stay under 10 requests a second. A 429 can also mean the monthly credit allowance is spent, so call /capabilities (free) before retrying
  3. Pass domains in lower case without www. or a path. The docs list 401 as data not found for a malformed domain
  4. Request only the metrics, countries and months needed. Credits multiply across domains, metrics, countries and periods, and daily granularity costs about 30 times monthly
  5. Website keywords accept monthly granularity for the last three months only, and position isn't returned for worldwide

Questions

Which is better for AI agents, Moz API or Similarweb?

Similarweb and Moz API score within a point of each other on agent readiness, 47.4 (D) and 46.7 (D). Moz API leads on reliability, agent ergonomics and payments & pricing.

Do Moz API and Similarweb need an API key?

Moz API needs an API key. Similarweb takes an API key or an OAuth sign-in.

Can an agent call Moz API and Similarweb without installing anything?

Yes. Moz API has a hosted endpoint at https://api.moz.com/jsonrpc and Similarweb at https://api.similarweb.com.

Other comparisons with Moz API or Similarweb

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.