Maps and places on VM0
Addresses, routes, places worth going to, and a map image for the report, without a Google Maps project of your own.
Location & weather · No setup · Managed credits per successful call
Anything that touches the physical world needs the same few answers. Where is this address. How long does it take to get there. What is nearby and is it any good. What does the area look like.
Google Maps and OpenStreetMap answer those, called and paid for by VM0, so there is no cloud project to create, no billing account to attach and no key to rotate. Place details come in a basic and a premium level, and the basic one is the default for a reason.
What Maps and places is
Location work always starts with turning an address into a point on the map, and often ends with a picture of the area in a document someone has to read.
The service covers both ends: geocoding an address and going back the other way, planning a route by car, on foot or on transit, searching for places and reading their details, and rendering a map image of an area.
Google charges more for its richer place details, so that choice is left in the open as a basic and a premium level rather than hidden. Basic is what you want unless a specific premium detail is genuinely needed.
Most people meet this as a Google Maps API key problem: a cloud project to create, a billing account to attach, a key to protect and Maps pricing to work out before anything can be looked up. None of that exists here. There is no key at all, because the call is made by VM0 and charged to your credits.
What Maps and places can do
What an agent can do with it, and what comes back when it does.
Coverage and limits
What it does not do, said up front, so nobody plans a workflow around something that is out of scope.
The coverage is the provider's
Quality follows Google Maps and OpenStreetMap. Dense cities are excellent, remote places are thinner, and neither is something VM0 can improve on your behalf.
Premium details cost more
The richer place details carry a higher charge. The level is asked for explicitly, so a workflow never quietly upgrades itself into a more expensive request.
Not live traffic or navigation
Routes answer the planning question, not the driving one. Live fleet tracking and turn-by-turn navigation are a different kind of product.
A map image, not an embedded map
The rendered image is a picture of an area for a report or a deck. It is not an interactive map you put inside your own product.
What Maps and places costs
Web services are billed in credits per call, not per token. There is no separate vendor bill to reconcile.
zero mapsMaps is charged in credits per successful call. The lever that matters is the level of place detail: keep it basic unless a premium detail is genuinely needed, because premium costs meaningfully more per call.
Setup and access
Nothing to set up
Nothing to connect. No Google Cloud project, no Maps billing account, no key and no key rotation. An agent can look up an address on its first run.
Who can use it
Maps is a permission granted per person and per agent, and taken back on its own without touching anything else the agent can do.
What teams use Maps and places for
Turning a list of addresses into something usable
A spreadsheet of customer addresses becomes locations, a map image and a set of travel times in one pass, rather than one afternoon.
Planning a visit
Given a place and a purpose, find the candidates, check what is actually nearby, and get the route with realistic travel times for how you will actually travel.
Putting a map in a report
A report or a deck gets a real map of the area in question, generated the moment the report is written instead of pasted in from a screenshot.
When not to use Maps and places
Skip it for live fleet tracking and turn-by-turn navigation, which need a purpose-built product. Skip the premium place details unless something specifically requires them. And do not use it as a company database: place data describes places, not businesses as businesses.
What this is called elsewhere
The same thing goes by several names in the market. If you have shopped for one of these, this is how it maps to what you get here.
A Google Maps API key you do not need
The usual first step is creating a key and attaching a billing account. There is no key here, nothing to rotate and no project of yours to keep an eye on.
Geocoding API
Turning an address into a location, and a location back into an address. It is the first step in almost every location workflow, including looking up the weather somewhere.
Places API
Searching for places near somewhere and reading their details, hours and ratings. Basic details are the default; the expensive ones are asked for explicitly.
Directions API
Routes and travel times by car, on foot or on transit, for planning rather than for turn-by-turn driving.
Static map image
A picture of an area to drop into a report or a deck, rendered from OpenStreetMap at the moment the report is written.
Maps and places compared
Maps and places vs your own Google Maps project
On your own it means a cloud project, a billing account, a key with the right services switched on, and alerts that wake someone when a workflow loops. Here the call and the bill sit with VM0, and access is a permission rather than a key.
Maps and places vs the Google Maps connector
The connector runs on your own key and your own Maps bill, which is what you want if you already have a Maps project and want the usage on it. This is what you want if you would rather not run one.
Maps and places vs OpenStreetMap on its own
OpenStreetMap is free and excellent for raw map data and images, which is why it is included here. Google's data is usually better for places, opening hours and ratings, so both are available rather than one being chosen for you.
The short version
Everything location without the cloud project. Look up addresses, plan routes, find places, render a map, all in credits. Keep place details on the basic level and it stays cheap.
Frequently asked questions
What is the difference between basic and premium place details?
They are Google's own pricing levels for place data. Basic covers the common details at a lower cost, premium adds the expensive ones, and the choice is always explicit.
Can it produce a map image?
Yes. It renders an OpenStreetMap picture of an area, around a point or across a rectangle, ready to put in a report.
Does it do live traffic and navigation?
It gives you routes and travel times. Live fleet tracking and turn-by-turn navigation are a different kind of product and out of scope.
Where does the data come from?
Google Maps for addresses, routes and places. OpenStreetMap for raw map data and rendered images.
Can I use Google Maps without an API key?
Through a VM0 agent, yes. VM0 holds the relationship with Google and charges the call to your credits, so you never create a cloud project, attach billing or hold a key.
How does this compare with Google Maps pricing?
Google bills your project per request, with the richer place details costing more. Here you pay VM0 credits per call, with the same basic and premium distinction, and no project or monthly bill of your own.
Is this a free geocoding API?
No. Looking up an address costs credits, but it costs nothing to set up. Weather is the service in this catalog that is currently free.
Can it geocode a whole list of addresses?
Yes. Each address is one lookup, so a spreadsheet becomes locations, travel times and a map in a single pass, and the cost is the number of addresses.
How you ask for Maps and places
You describe what you want in plain language. The agent works out which service it needs and makes the calls.
“Find three well-reviewed coffee shops near Union Square in San Francisco and give me the walking route to the closest one.”
“Take these fifty addresses, work out drive times from our office, and put the map in a one-page summary.”
“Add a map of the area around this site to the report, centred on the address.”