The Semantic Research API documentation is not publicly available. The company specializes in knowledge structures which primarily have to do with law enforcement and intelligence.
When a federal judge declared in June that software APIs aren’t covered by copyright law, it was a major victory not just for Google against Oracle, but for the API developers and users alike.
Rpost made its name in the compliance space through its Rpost API and core products: email proof, privacy, and electronic signatures. Rpost’s core offering won a customer list full of household names across many industries, both public and private (Whole Foods, AT&T, and Civpol to name a few). Rpost now aims to bring its compliance strategy to all internet transactions via RPost Cloud.
Law practice and case management software has been around for years. These Programs gave lawyers the ability to focus on what they love to do and simplified the recurring tasks that are incurred when running a law practice. However, many lawyers don’t work solely from the comfort of their office where these tools have been easily accessible in the past. Thankfully, we now have “Cloud Based Law Practice Management”, allowing lawyers to access the tools that they use to manage day to day operations anywhere that they have an internet connection.
The Google Maps API took a hit in France as non-competitive. The Gnip API now lets its customers go back in time, tweet-wise, retroactively tracking specific terms. Plus: APIs for hustlers, putting the “why” in user permissions and 10 new APIs.
Sniffing for API calls from mobile applications has become the hip new way to open platforms that aren’t yet ready for outside developers. Usually broadly-written terms and conditions essentially forbid this sort of usage, but it still happens. Snark.ly, a new iPhone app for people to share their funny one-liners, has gone a step further and expressly forbids the use of its private API in its terms.
One of the questions we are often asked at 3scale (a ProgrammableWeb sponsor) is around legal terms and conditions (T&Cs) – once we have all the technical stuff, what should we put in the API terms and conditions? Should they be different from our web site terms and conditions? What will the impact of certain clauses be? Since we’re not a law firm, we generally can’t answer this question in detail but there are a few recurring themes we often see in T&Cs that seem worth sharing. The content of this post should not be taken as legal advice in any way, but hopefully it provides some useful things to consider.
Avvo, the lawyer and doctor directory we profiled last week, has recently opened its Avvo API for wider use. To understand Avvo’s plans for its API, we spoke with Joshua King, Vice President, Business Development & General Counsel at Avvo. It is interesting to note that Avvo prioritized the release of its API over other opportunities that it had. Read the full Q & A with King below:
Lawyers and Doctors have a special place in our society. Most of us need them at some time or the other. Avvo is a directory focused on lawyers and doctors, allowing us to search them based on their area, expertise, user ratings and other criteria. Now its Avvo API provides the same functionality to your applications.
There are no secrets on the Internet. And now, thanks to StealthModeWatch, it’s even easier for people to find your secrets–if you’re a company with outside investors. The service, which also includes an API, digs through public records to expose new investments and the people attached to them.