Hi, cofounder here. Thanks for looking and your feedback! Yes, pricing is something we're still debating on and hope to decide by next week - whether to a char

Hi, cofounder here. Thanks for looking and your feedback! Yes, pricing is something we're still debating on and hope to decide by next week - whether to a charge a flat rate per request or to make it dependent on computing resources used. As for private vs public services, the wording could definitely be clearer - it basically determines if requests can be made to a service by anyone or if authentication and tokens are required. I understand the confusion tho, it came about as we were initially looking to create a GitHub of live APIs that would all be public however users told us they were more interested in hosting their own private code. Yep, language support and pricing are massively important for us, we aim to get most other dynamic languages supported ASAP (ES6 and Python already there, Ruby on the way) and follow with compiled languages after (Go is top of the list). Thanks again - super useful and would love to hear how you got on if you decided to deploy a service!