One thing that confused me in the API documentation that it seems to use "concepts" and "words" to mean the same thing. "word" made me think it has some kind of linguistic proximity check, though I'm quite sure that's not what what your API is about. Later examples use phrases instead of words, so it seems that 'word' is the wrong word here - please ban it completely.
From a quick skimming I didn't find if the relationships for all API keys are stored separately, or if all the data is meshed together in one central place (I guess it's the latter, but I'm not sure).
I'm also a bit confused that the examples indicate client side Javascript, and still one needs an API key, but if one uses that API key, it'll be available for the user, and thus not a secret, which seems to defeat the whole purpose. What's the point?
I hope that gives you some ideas for clarifications.
One thing that confused me in the API documentation that it seems to use "concepts" and "words" to mean the same thing. "word" made me think it has some kind of linguistic proximity check, though I'm quite sure that's not what what your API is about. Later examples use phrases instead of words, so it seems that 'word' is the wrong word here - please ban it completely.
From a quick skimming I didn't find if the relationships for all API keys are stored separately, or if all the data is meshed together in one central place (I guess it's the latter, but I'm not sure).
I'm also a bit confused that the examples indicate client side Javascript, and still one needs an API key, but if one uses that API key, it'll be available for the user, and thus not a secret, which seems to defeat the whole purpose. What's the point?
I hope that gives you some ideas for clarifications.