I don't believe we offer TTS as a service, but I'll ask around. Generally speaking, when we have a public API we both document the API on code.google.com and provide explicit Terms by which the API may be used. For example, the Google Translate API Terms:
http://code.google.com/apis/language/translate/terms.html If you don't see developer documentation for a product, and you don't see developer Terms, then you're likely looking at a consumer-facing product. Consumer products (and all developer products, too) are all covered under our general Google Terms of Service: http://www.google.com/accounts/TOS Of course, many of our consumer facing web-based products are built using plenty of Ajax (no surprises there), and as such provide *private* endpoints to make the products work. However, unless those endpoints are publicly documented and explicitly covered under developer-facing Terms, they're designed for internal usage only, will likely change or break over time, and thus shouldn't be accessed by external developers. Section 5.3 of the Google ToS (linked above) may also be of particular interest here. That said, we're always building new APIs, and love to hear your ideas for new ones. I'll be sure to pass along the request for a TTS API, for example. And as to why we're quiet sometimes when people ask specific questions about the ToS, we're actually not allowed to comment much on interpretations of the Terms, much as we might want to help. The worst thing we can do for you (according to our lawyers, and I believe them) is give conflicting or confusing advice to you (we're not lawyers, after all, and we're definitely not *your* lawyer). So for the most part we do what Jeremy does and suggest you talk to your own counsel if you have any doubts. We can, however, talk about the APIs in general and point people to the right places for more information, so please don't hesitate to ask. The worst thing that happens is that we can't answer specifically, but at least the question is out there. -DeWitt On Thu, Mar 17, 2011 at 12:03 PM, Zdravko Gligic <[email protected]> wrote: > As far as I am concerned, I would gladly pay GOOG a flat $25 fee to > spend 5-10 minutes looking at each of my apps / uses cases - within 5 > business days of me submitting a Google Checkout payment. > > I (the little guy) would gladly pay GOOG (the giant) to cover its > costs of protecting its own interests, while at the same time freely > building up its own business. I would gladly pay because what is now > is baddly ineffective. > > -- > You received this message because you are subscribed to the Google Groups > "Google AJAX APIs" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-ajax-search-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
