[wolfrom]

We are wary of the issue of dependency as well. As you point out, there are ways of mitigating the risk, and we are making it a top priority:

1. Stability and security will be maintained by a gradual roll-out and a user-driven testing phase. We're still working out the details on this.

2. A standard documentation format is a key requirement for each documented API call; no call will be released for general usage until it has all included information (parameters, possible success and error results, example response).

3. Pricing / service contracts. We are looking at providing guarantees on pricing stability and uptime, and we're thinking of not charging in advance, but after service has been rendered.

4. Source release pledge. It's too early to know how to proceed with open sourcing, but we do expect that at a minimum our client libraries will be open source. And we will pledge to release all code if there were to be an impending service shutdown, with three months minimum for transition.

I think that's all we can do when starting out to show that we aim to be a reliable component. The real evidence probably can't come until we earn a reputation over the coming months.