Thank you very much for your kind understanding.
Alex.

Hi Alex!

Thank you for the clarification. I am the author of Microstock Report, an Android widget that shows microstock earnings. My app is installed on about 200 phones and checks the earnings twice an hour. If I imagine a rainy day scenario (each user has the phone turned on all the time, with the widget on their homepage, everyone has 123RF account enabled), it's approximately one request each 10 seconds. I have to log in, download commission_stable_ajax.php, parse it and find the earnings. That's quite a lot of work for both my app and your server, I agree with that (and that's just one little widget with really few users).

If I could use a public API, I'd send one POST request and get a small XML back - and that's it. Less work for my app (and for my users' phones), less bandwidth for your server. And we both would benefit from such API - if your contributors can check their earnings on their phones, they don't have to log into your site to do it. And logging into your site requires far more bandwidth due to all those images, scripts and styles they need to download.

Having said that, the only question that remains is: Do you have any idea how fast you could create such API?