Create the instant account at now!

The recommendation domain consists of three principal components:

We assume that there is a catalog of items that are available to users. Users may interact with the items:

  • View details about them (if there is an information page for each item present in your system).
  • Rate them (explicit rating submitted by users, may also be negative),
  • Purchase them (~ read the whole article, view most of a video ... depending on your domain),
  • Bookmark them (add them to a wishlist, or mark them as favorites),
  • View some portions of them,
  • or Add them to cart.
Server side integration

Server side integration

Client (.js) & server side integration

Client (.js) & server side integration

Besides their ID, the items and users may have certain properties. The properties are analyzed by the recommender to further improve the recommendations. Also, you may use the properties to filter or boost recommendations of some specific items. The set of properties is managed by the API user, who may define properties according to the target domain. The properties may be thought as columns in relational database table: they are of certain types and they may be of specific values for different items.

Recommendation endpoints can return items, which is the most common case, or users.

We provide client libraries (SDKs) for easy use of our API.