May I sell software I build that uses the API?

[Michael Kaufman]

I have developed a little application for myself that uses the Google Maps API and we thought it might be perfect for businesses. I would like to bundle it up and offer it for sale.

Is this breaking any of the Maps terms of use to sell a program which accesses the Google Maps API V3?

I read the documentation but I'm still a little confused on the topic.

[JKurtock]

"10.1.2 Restrictions against Commercial Use." seems to pretty clearly
bar selling any software that uses the API. (Note that there is an
express exception for Mobile Apps available through a sort of app
store. But I doubt you were thinking of that when you said it was
"perfect for businesses.")

OR, of course, you can enter into a Google Enterprise Agreement.
http://www.google.com/enterprise/earthmaps/maps.html

Is there something you saw that suggested you could sell your software
without an agreement with Google?

- Jeff

On Aug 5, 10:19 am, Michael Kaufman <michael.allan.kauf...@gmail.com>
wrote:

[MymsMan]

I believe that I may be in a similar position to Michael.

I have created an app that I think many companies would like to incorporate on their websites.

I believe that I am entitled to ask those companies to pay me for my efforts in developing the app and supporting it.

See 9.1.3 c in the Ts&Cs

What is not permitted (without an enterprise agreement) is for me or the companies hosting my application is to then charge end users for the privilege of using the application.

If I am misunderstanding the Ts&Cs I would appreciate clarification before I proceed further.

[Mark Liversedge]

What if, as a consultant/freelance, I develop something for a client. I am selling my services not the software. Would they need an enterprise licence?

[Andrew Leach]

On 6 August 2011 13:20, Mark Liversedge <liver...@gmail.com> wrote:
> What if, as a consultant/freelance, I develop something for a client. I am
> selling my services not the software. Would they need an enterprise licence?

No. See 9.1.3(c).