• * Unprecedented flexibility for anyone, from a blogger in Pittsburgh to KQED in San Francisco, to generate highly specific content searches of the NPR archive (going back to 1995) and port the results to a webpage or an application.
• * A number of stations also have their archives inside the system, too. So queries can also include (or not) results from those stations.
• * If more stations are allowed to contribute their content metadata to the API, the search query delivers better and more complete results, encompassing more of the output of the entire public radio system.
• * NPR content (and our content, when we join the API) begins appearing all over the web, and yes, this doesn’t diminish the value of our work or our web sites; it INCREASES its value as more people encounter and discover it, and click on the links to read more.

Those points are big but that last point is BIG.

The average public radio listener visits her public radio station web site twice a MONTH.

Yes, we’re all working to add value to our sites and increase visits; we must continue to do this. (We’re busting ass on this at Louisville Public Media’s three stations and we’re seeing some great results – details to be revealed in a few months.) But when that content appears on other platforms, that’s when we’ll have a much bigger audience for what we do.

Back to that average public radio listener: she may visit publicstation.org only twice a month, but she reads a set a 10 favorite blogs twice a day. If even one of those blogs uses the API to “curate” a selection of your stories, or installs a widget like this one, guess how much you’ve increased the potential of listeners discovering your content? And clicking over to your web site to read more?

There’s more to be said about other benefits of this… but this is what makes me very excited about what NPR’s Digital team has done… what NPR management has approved.

A technical fog can descend over stories like this, but it shouldn’t. This is a BIG deal.

10am UPDATE: It’s now live. Here’s Daniel Jacobson’s post.

This is a pretty big deal… a signal of openness from NPR, a willingness to let developers have access to NPR’s content, and the beginning of what could be some really cool stuff.

What is an API? Here’s a definition only a developer could love. Here’s my somewhat mangled definition: API is an Application Programming Interface. It’s a set of tools developers can use to access parts of one web site and integrate it with another site or application. Examples? Those applications you add to your Facebook page, those cool applications that plot everything from crime data to photos on Google Maps.

NPR promises a gallery to showcase widgets when the API launches; the blog includes a link to Reverbiage, which plots NPR stories on a world map. That’s a widget I’d love to display on one of WFPL‘s News pages. There’s also a nice iPhone app from Axiom Stack. Probably the best thing about an API is that developers anywhere with good ideas can build applications that can organize and present NPR’s content in all kinds of interesting ways.

An API was one of the least sexy recommendations of the Digital Distribution Consortium – remember that? The group was hard at work two years ago at this time, trying to find ways to present a more coherent way to present public radio online.

Some of the DDC recommendations were fought over, some ignored. But, hey, NPR is about to give us, and developers everywhere, the opportunity to create new tools that add value to NPR’s (and our own) content.