Skip to main content

Google Maps Platform

Geocode addresses, search places, and build maps and directions with your Maps API key.

Connect it with: API key. Google Maps Platform's own documentation: https://developers.google.com/maps/documentation/javascript/get-api-key.

What agents can do​

Connect Google Maps Platform so the agents working your tasks can reach it. With it connected, they can:

  • Geocode an address to coordinates, or reverse-geocode coordinates to an address.
  • Search places by text or near a point, and read a place's details and opening hours.
  • Compute routes, distances and travel times between addresses.
  • Wire a Maps JavaScript or Static Maps key into an app's configuration while building it.

Before you start​

  • A Google Cloud project with billing enabled. Google Maps Platform does not serve keys from a project without a billing account.
  • Each Maps API agents call enabled in that project (Google Maps Platform > APIs & Services).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Google Maps Platform​

Jaah connects to Google Maps Platform with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API key: Google Cloud console > Google Maps Platform > Keys & Credentials > Create credentials > API key. Restrict it under API restrictions to the Maps APIs agents need (for example Geocoding API and Places API) before saving it here.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Google Maps Platform card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Google Maps Platform with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah checks that each value has the right shape, but does not call Google Maps Platform: the result reads Format checked — Google Maps Platform was not called. The first real check is when an agent uses it.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Google Maps Platform secret org/google-maps”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Google Maps Platform once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Google Maps Platform's side too, revoke or delete the key at Google Maps Platform.

Limitations​

  • Jaah's Test checks only the key's shape and does not call Google, because every Maps request is billed. The first real check is an agent's first call.
  • Every agent call is billed to your Google Cloud project at Google's per-SKU price. Set a budget alert and per-API quotas in the Cloud console.
  • A key restricted to HTTP referrers (websites) is refused from servers. For agents, use a key restricted by API, or by IP address.
  • Agents can do only what the connected Google Maps Platform account allows.

Troubleshooting​

Test says API key is not in the format Google Maps Platform uses

Google API keys start with AIza and are 39 characters. Copy the key again from Keys & Credentials > Show key, without spaces or quotes.

An agent gets REQUEST_DENIED with This API project is not authorized to use this API

Enable that API (for example Places API) in the project, and add it to the key's API restrictions.

An agent gets REQUEST_DENIED with You must enable Billing

Link a billing account to the project in Billing > Account management.

An agent gets The provided API key is invalid although the format check passed

The key was deleted or belongs to another project. Create a new key and select Replace on the secret.

Still stuck? Select Test and read the result: it names the first value that is missing or not in the shape Google Maps Platform uses. It does not call Google Maps Platform, so Google Maps Platform's own errors show only in the agent's session.

FAQ​

Why is the Test only a format check?

Google bills every Maps Platform request, including the cheapest read, so testing would cost money on every save. The format check catches typos; the first agent call proves the key.

Can I reuse the key from my website?

Better not: a website key is usually restricted to HTTP referrers, which servers cannot send. Create a separate key for agents.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Google Maps Platform account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.