From their site: Akismet is basically a big machine that sucks up all the data it possibly can, looks for patterns, and learns from its mistakes. Thus far it has been highly effective at stopping spam and adapting to new techniques and attempts to evade it, and time will tell how it stands up. I\'ve tried to keep the API interaction as simple as possible. To interact fully with the Akismet API your program really should be putting data back into the system as well as just taking it out. If it is at all possible within the framework of your application you should have a way for your users to submit missed spam and false positives, otherwise Akismet will never learn from its mistakes.
The following is a list of how-to and tutorial content that matched your search term. ProgrammableWeb's how-to content comes from two sources; full-blown tutorials that we publish ourselves and other highly relevant tutorials that we find elsewhere on the Web. This list represents on combination of both tutorial types and if you go to ProgrammableWeb's API University, you'll not only be able to find more, they are organized based on your role (API providers or developers who consumes APIs). If you know of a tutorial that would be of interest to the ProgrammableWeb community, we'd like to know about it. Be sure to check our guidelines for making contributions to ProgrammableWeb.