Google Maps Address & Coordinate Geocoding Lookup

What it returns

25 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

• recordType
• mode
• inputAddress
• inputLocation
• inputPlaceId
• resolved
• name
• formattedAddress
• location
• placeId
• featureId
• plusCode
• addressComponents
• categoryName
• timezone
• countryCode
• resultLevel
• distanceMeters
• googleMapsUrl
• sourceUrl
• scrapedAt
• plusCodeGlobal
• plusCodeCompound
• categories
• language

Not in the schema among the core Google Maps fields: phone, website, rating, reviews, hours, latitude, longitude. The field matrix shows which other tools return them.

How it differs from the other Google Maps Actors

Among the 17 catalogue Actors for Google Maps with a published schema, only this one returns resultLevel.

Pick another Actor if you need

Input

Example input

Built from the input form's published example values and defaults.

{
  "mode": "forward",
  "addresses": [
    "1600 Amphitheatre Parkway, Mountain View, CA"
  ],
  "language": "en"
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "forward",
    "addresses": [
        "1600 Amphitheatre Parkway, Mountain View, CA"
    ],
    "language": "en"
}

run = client.actor("vexaloom-labs/google-maps-address-and-coordinate-geocoding").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "mode": "forward",
    "addresses": [
        "1600 Amphitheatre Parkway, Mountain View, CA"
    ],
    "language": "en"
};

const run = await client.actor("vexaloom-labs/google-maps-address-and-coordinate-geocoding").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~google-maps-address-and-coordinate-geocoding/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"forward","addresses":["1600 Amphitheatre Parkway, Mountain View, CA"],"language":"en"}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=vexaloom-labs/google-maps-address-and-coordinate-geocoding",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

• Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
• The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
• Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
• Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

Where it fits among Google Maps routes

It ranks 16 of 17 catalogue Actors for Google Maps on the published formula (fields, price, reliability, freshness). Its line is highlighted on the map.

What people use it for

• Geocode addresses
• Resolve coordinates to addresses

Other catalogue Actors for Google Maps

Similar Actors

Questions people ask

Sources

• Google Maps Address & Coordinate Geocoding Lookup on Apify Store
• Published build with input and output schema (JSON)
• Google Maps Platform Places API documentation