Are all those loads needed? In other words, how often do people interact with them? (Figuring how often they look at them is even more effort.) This kind of changes usually are made to discourage inefficient use of the API, which could be delayed until specific events happen: scrolling, mouseover, timer, etc. I'm not saying that's necessarily your case.

I can probably lower the loads somewhat, but I use other maps services too (street view, etc.) and this $200 free credit seems like for all of the services combined monthly, so one does not get a $200 free credit for each service and costs will quickly add up.

Makes sense.

I see that the limit you mention is for dynamic maps. Somewhere else, they say "Requests for Dynamic Maps and Dynamic Street View (Street View Panoramas) will be billed at a higher rate than requests for Static Maps and Static Street View. Dynamic Maps and Street View images respond to user input; the Static versions do not."

I imagine that this is an incentive for developers to use static maps (which you could replace with dynamic ones when the user clicks or hovers on them). If you used static maps alone, that's 300K loads per month, or $480. You would deduct the $200 credit, for a $280 bill, but then pay full price for all the other services. I can see how that adds up quickly...

you got 30 days. hope you got nothing else planned... ruins my current roadmap.