Ambee MCP integration for AI agents.
Connect AI agents to Ambee through 5 structured actions, including get air quality by lat lng, geocode by place, and get air quality forecast by lat lng. Rev…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Ambee integration exposes
The Ambee Agent App exposes 5 provider-backed actions for location and data work. Its current contract lets an authorized agent get the latest air quality station readings for one coordinate from ambee, convert a place name or address into latitude and longitude with ambee, and get the air quality forecast for one coordinate from ambee. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Ambee account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ambee capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_air_quality_by_lat_lngREADGet the latest air quality station readings for one coordinate from Ambee.
INPUTS: lat / lng
geocode_by_placeREVIEWConvert a place name or address into latitude and longitude with Ambee.
INPUTS: place
get_air_quality_forecast_by_lat_lngREADGet the air quality forecast for one coordinate from Ambee.
INPUTS: lat / lng
get_air_quality_history_by_lat_lngREADGet historical air quality readings for one coordinate from Ambee.
INPUTS: lat / lng / from / to
reverse_geocode_by_lat_lngREVIEWConvert latitude and longitude into location details with Ambee.
INPUTS: lat / lng
INPUT CONTRACTS
Know what the action needs before it runs.
get_air_quality_by_lat_lng
latOPTIONAL- The latitude of the target location.
lngOPTIONAL- The longitude of the target location.
geocode_by_place
placeOPTIONAL- The place name or address to geocode.
get_air_quality_forecast_by_lat_lng
latOPTIONAL- The latitude of the target location.
lngOPTIONAL- The longitude of the target location.
get_air_quality_history_by_lat_lng
latOPTIONAL- The latitude of the target location.
lngOPTIONAL- The longitude of the target location.
fromOPTIONAL- The timestamp in `YYYY-MM-DD hh:mm:ss` format required by the Ambee history endpoint.
toOPTIONAL- The timestamp in `YYYY-MM-DD hh:mm:ss` format required by the Ambee history endpoint.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Air Quality By Lat Lng
Get the latest air quality station readings for one coordinate from Ambee. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_air_quality_by_lat_lngVerify with Get Air Quality Forecast By Lat Lng
Get the air quality forecast for one coordinate from Ambee. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_air_quality_forecast_by_lat_lngSAFETY BOUNDARY
Operate Ambee with explicit limits
- Authorize Ambee with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Ambee data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Ambee rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ambee task completed successfully.
CONNECTION MODEL
API key
Ambee API key sent with the x-api-key header. Create or copy it from the Access API Keys page in your Ambee account: https://docs.ambeedata.com/access-api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Ambee.