Javascript Maps Api V3 Quotas, How Do They Work?

I need to access all sorts of map data through Google Maps and I'm trying to figure out how the quota's and installation works. From the reading I've done, it seems that with JavaS

Solution 1:

The APIs all have their own keys, which you activate via the API console, but are all accessed (in the case of a JS Maps application) through your single Maps API key.

The main thing that they don't make particularly obvious, is that for Javascript applications, the quota is per-client, so your limit essentially scales to your user-base.

I asked a similar question here, and the response I got (as well as my own research and experimentation) backs that up:

Regarding Places Library for Google Maps API Quota limits

If you want to test this, create a dummy JS app which queries one of the libaries a couple of times, and check the quota on your API console - it should be zero. However, if you curl the same query from the command line, it will increase the quota.

Solution 2:

There are two ways to access these APIs:

1. As a JavaScript API v3 library/service
2. As RESTful HTTP Web Service

For the JavaScript API, only map loads are counted and you could in theory perform as many services calls as you want. However, you will run into OVER_QUERY_LIMIT responses if you just hammer the service with requests. (see for example this question)

For the RESTful web services, the limits you already found apply.