It would actually be pretty easy to write, but it falls under question #7 of
our suggestions FAQ. Once we allow our data to be taken off our site, we're dealing with a potential problem:
We have an
ungodly amount of data. The site has been recording every transaction by every character on every server for going on 2-3 years now. Not to mention character records, profile scan histories, linkshell memberships, forum and private messages... suffice to say our poor database server has its work cut out for it.
Having all of the data only available through one online format allows us to pull a lot of crafty tricks behind the scenes regarding our data partitioning and calculations. We can control how the data is queried and which data is readily available, which is archived, which is held aside for other computations, etc. This is what allows us to keep serving up transaction histories on request with less than a second delay -- otherwise, it could take the site 20-30 seconds to complete every request to display a page, due to the sheer amount of data it would have to slog through.
Once we open the data to outside queries, however... we lose a lot of this. We can no longer make assumptions about how the data will be used, so our efficiency tricks would be nullified. Site performance would likely suffer for everyone. In order to offset this, we would probably need to upgrade all our servers and start clustering data out, etc... which is more expensive, meaning we would likely have to charge a fee to access our data from off-site through some kind of API, especially given that you wouldn't be hitting our ads, so we'd be losing revenue... and to do that we'd need to set up a billing system back end to handle all the...
Yadda yadda etc etc. It gets very messy and complicated very fast, and so far, we haven't felt it was worth it. It's still on the table for the future, however.