I've created SDKs (REST API wrappers) in Python, PHP, Ruby, Java, C#, Android for the WordsAPI:
(Objective C, Scala, ActionScript SDKs still in beta)
Hope these SDKs make it easier for developers to consume the API.
For a more comprehensive word API, check out the excellent Wordnik API: http://developer.wordnik.com/docs.html#!/word
And Wordnik is becoming a not-for-profit, if that makes a difference to you. :-)
Disclaimer: I am the founder of Wordnik. (You might like my TED talk: http://www.ted.com/talks/erin_mckean_redefines_the_dictionar...)
That said, I know the guy behind WordsAPI and he's good people. :-)
Otherwise, all requests require an access token.
Interesting! I never realized this.
What if you give a % of your revenue to them to help them, in return you could be the recommended API on their site?
Since there have been so many requests, most common words are in Redis at this point.
Imagine something akin to tab completion for writing prose.
Basic rule of thumb for writing prose: synonyms are a myth. No two words have exactly the same meaning.
One issue I found is that it provides alternative spellings as distinct items. Is there a workaround for this?
One question though, does anyone have any idea what the copyright for this would be? If you happen to use X dictionary (one for each implemented language for example, or even maybe as a selectable source), would say, the Oxford Dictionary could sue because you are using their data? AFAIK, facts are not copyrightable, are they? where would this stand?
For example, instances of "aqua" should probably match the search query "blue". Google seems like it may already be that advanced, but other search engines perhaps not. Large-scale search engines probably would keep this in their own DB, though.
Nice project! What about adding example of sentences?
Ontology engine? If so, what's your source?