Google Pollen API

Name: Google Pollen API API
Brand: Google Pollen API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey2 EndpointsREST

For Agents

Look up 5-day pollen forecasts (grass, tree, weed) for any latitude/longitude and fetch heatmap tiles via two Google Pollen API endpoints behind a Google Maps API key.

Quickstart

Get started with Google Pollen API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get a pollen forecast for a location"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Pollen API API.

Get a 1-5 day pollen forecast for a coordinate via GET /forecast:lookup with latitude, longitude, and days

Render pollen heatmap tiles by zoom and x/y via GET /mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y}

Filter forecasts by plant type (grass, tree, weed) using the plant detail flags on the lookup endpoint

Localise category descriptions and recommendations by passing a languageCode on the lookup endpoint

GET STARTED

Start building with Google Pollen API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Google Pollen API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Google Pollen API, keeping it validated and agent-ready. Google Pollen API (formerly BreezoMeter Pollen) is part of Google Maps Platform and returns up to five days of pollen information at 1km resolution across more than 65 countries. Two endpoints cover the use cases: a JSON forecast lookup at GET /forecast:lookup that takes latitude, longitude, and an optional days range, and a heatmap-tile endpoint at GET /mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y} for rendering pollen layers on a map. Authentication is a Google Maps API key passed as the key query parameter, which makes the API straightforward to wire into health, allergy, and weather applications.

Use Cases

Patterns agents use Google Pollen API API for, with concrete tasks.

★ Allergy and wellness app forecasts

Power an allergy app that shows users the pollen forecast for their home and any saved locations. The client geocodes the location, then calls GET /forecast:lookup with location.latitude, location.longitude, and days=5 to get per-plant indexes. Localised category descriptions support multilingual users without bespoke translation work.

GET /forecast:lookup with location.latitude=40.7128, location.longitude=-74.0060, days=5, languageCode='en' and return the dailyInfo array with pollenTypeInfo per day.

Pollen heatmap layer on weather maps

Add a pollen heatmap layer on top of a base map so users can see where pollen is concentrated regionally. The frontend requests heatmap tiles by zoom/x/y from GET /mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y}, choosing a mapType such as TREE_UPI, GRASS_UPI, or WEED_UPI. This is the same tile flow used in Google Maps Platform overlays.

GET /mapTypes/TREE_UPI/heatmapTiles/8/72/96 (with key) and render the returned PNG as a tile in the map's pollen overlay.

Outdoor activity planning

Help runners and cyclists plan workouts on lower-pollen days. The backend reads GET /forecast:lookup for the next five days and recommends outdoor sessions when the worst plant index falls below a configured threshold. Plant-specific filtering supports users with a known sensitivity to grass or ragweed.

GET /forecast:lookup for the user's location with days=5; for each day, take the maximum pollenTypeInfo[].indexInfo.value and surface days where the max < 3.

AI agent integration via Jentic

An agent answering 'how bad is the pollen tomorrow at my address?' can discover the Google Pollen API through Jentic, load the forecast lookup operation, and execute it without holding the Maps API key in its prompt context. Jentic injects the key as the query parameter at execution time and returns typed forecast data the agent can summarise.

Through Jentic, search 'get a pollen forecast for a location', load the GET /forecast:lookup operation, and execute with location.latitude, location.longitude, and days=3.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for google pollen api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/forecast:lookup

Pollen forecast for a latitude/longitude over 1-5 days

GET

/mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y}

Pollen heatmap tile for a map zoom level

GET

/forecast:lookup

Pollen forecast for a latitude/longitude over 1-5 days

GET

/mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y}

Pollen heatmap tile for a map zoom level

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Maps API keys for the Pollen API are stored encrypted in the Jentic vault and appended as the key query parameter at execution time. Agents call the forecast and tile operations by intent without ever embedding the raw key in code or prompts.

Intent-based discovery

Agents search Jentic for intents like 'get a pollen forecast for a location' and Jentic returns the GET /forecast:lookup operation with location.latitude, location.longitude, and days parameters typed, plus the heatmap-tiles operation when the agent needs imagery.

Time to first call

Direct Pollen API integration: a few hours to handle key restrictions, response parsing, and tile rendering. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BraveNewCoin API

Different domain — BraveNewCoin returns crypto market data, not environmental forecasts

BraveNewCoin is unrelated; listed only when an agent has confused environmental and market-data intents — choose Google Pollen for pollen forecasts.

Complementary

Braze Endpoints

Trigger Braze customer messages when the Pollen API forecasts a high index in a user's region

Use Braze when the agent needs to deliver a pollen alert message to users; use Google Pollen to compute the index that triggers it.

Complementary

Breeze API

Schedule outdoor-event tasks in Breeze conditioned on Pollen API forecast levels

Use Breeze to track tasks; use Google Pollen to source the forecast input that decides when to schedule them.

FAQs

Specific to using Google Pollen API API through Jentic.

Why is there no official OpenAPI spec for Google Pollen API?

Google Maps Platform documents the Pollen API in narrative form rather than publishing a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Google Pollen API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Google Pollen API use?

It uses a standard Google Maps API key passed as the key query parameter on every request. Restrict the key by HTTP referrer or IP in the Google Cloud Console; through Jentic, the key is held in the encrypted vault and appended to /forecast:lookup and tile requests at execution time.

How many days of pollen forecast does the Google Pollen API return?

GET /forecast:lookup returns up to 5 days of pollen information when you pass days=5. Coverage spans more than 65 countries at 1km resolution, with separate indexes for tree, grass, and weed pollen on each day.

What are the rate limits for the Google Pollen API?

Pollen API quotas are managed through the Google Cloud Console as part of Google Maps Platform — daily request quotas and per-second QPS are configurable per project. Check your Cloud Console quotas page before fanning out heatmap-tile requests across many zoom levels.

How do I get a pollen forecast through Jentic?

Install with pip install jentic, then await client.search('get a pollen forecast for a location'), await client.load on the GET /forecast:lookup operation, and await client.execute with location.latitude, location.longitude, and days. Jentic appends the Maps API key at execution time.

Does the Google Pollen API support heatmap tiles?

Yes. GET /mapTypes/{mapType}/heatmapTiles/{zoom}/{x}/{y} returns PNG tiles for tree (TREE_UPI), grass (GRASS_UPI), and weed (WEED_UPI) heatmap layers. Use them as a tile overlay on a base map alongside the forecast lookup data.