Api matchmaking using feature models

A computer program product comprising a computer readable storage medium having stored thereon:

• first program instructions programmed to receive a set of application programming interface (API) terms-of-service (ToS) feature information that includes identifying information for at least one API and respectively associated ToS features for each identified API;
• second program instructions programmed to receive ToS preference information that relates to ToS related preferences for a user;
• and
• third program instructions programmed to evaluate a strength of a match between each respective API identified in the API ToS feature information set and the ToS preference information to yield a match value for each API identified in the API ToS feature information set;
• wherein:
• the respectively associated ToS features include at least a first ToS field;
• and
• at least one API identified in the API ToS information set includes multiple, alternative values in its respectively corresponding first ToS field.

A computer system comprising:

• a processor(s) set;
• and
• a computer readable storage medium;
• wherein:
• the processor set is structured, located, connected and/or programmed to run program instructions stored on the computer readable storage medium;
• and
• the program instructions include:
• first program instructions programmed to receive a set of application programming interface (API) terms-of-service (ToS) feature information that includes identifying information for at least one API and respectively associated ToS features for each identified API;
• second program instructions programmed to receive ToS preference information that relates to ToS related preferences for a user;
• and
• third program instructions programmed to evaluate a strength of a match between each respective API identified in the API ToS feature information set and the ToS preference information to yield a match value for each API identified in the API ToS feature information set;
• wherein:
• the respectively associated ToS features include at least a first ToS field;
• and
• at least one API identified in the API ToS information set includes multiple, alternative values in its respectively corresponding first ToS field.