Radar MCP integration for AI agents.
Connect AI agents to Radar through 5 structured actions, including search places, autocomplete, and forward geocode. Review authentication, inputs, workflows…
- 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 Radar integration exposes
The Radar Agent App exposes 5 provider-backed actions for location and data work. Its current contract lets an authorized agent search radar places near coordinates by chain or category, autocomplete a partial address or place name with radar, and convert a complete address into coordinates with radar. 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 Radar account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Radar capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
search_placesREADSearch Radar places near coordinates by chain or category.
INPUTS: latitude / longitude / chains / categories / radius
autocompleteREVIEWAutocomplete a partial address or place name with Radar.
INPUTS: query / latitude / longitude / layers / limit
forward_geocodeREVIEWConvert a complete address into coordinates with Radar.
INPUTS: query / layers / country / lang
ip_geocodeREVIEWGeocode the connector request IP with Radar.
reverse_geocodeREVIEWConvert coordinates into nearby addresses with Radar.
INPUTS: latitude / longitude / layers
INPUT CONTRACTS
Know what the action needs before it runs.
search_places
latitudeREQUIRED- The latitude coordinate in WGS84 decimal degrees.
longitudeREQUIRED- The longitude coordinate in WGS84 decimal degrees.
chainsOPTIONAL- Radar chain slug filters sent as a comma-separated list.
categoriesOPTIONAL- Radar category filters sent as a comma-separated list.
radiusOPTIONAL- The search radius in meters.
autocomplete
queryREQUIRED- The partial address or place name to autocomplete.
latitudeOPTIONAL- Optional latitude used with longitude to prefer nearby autocomplete results.
longitudeOPTIONAL- Optional longitude used with latitude to prefer nearby autocomplete results.
layersOPTIONAL- Radar result layer filters sent to Radar as a comma-separated list.
limitOPTIONAL- The maximum number of results to return.
forward_geocode
queryREQUIRED- The complete address to geocode.
layersOPTIONAL- Radar result layer filters sent to Radar as a comma-separated list.
countryOPTIONAL- Country filters sent to Radar as a comma-separated list of two-letter country codes.
langOPTIONAL- The language code used to localize Radar results.
reverse_geocode
latitudeREQUIRED- The latitude coordinate in WGS84 decimal degrees.
longitudeREQUIRED- The longitude coordinate in WGS84 decimal degrees.
layersOPTIONAL- Radar result layer filters sent to Radar as a comma-separated list.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Search Places
Search Radar places near coordinates by chain or category. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
search_placesVerify with Autocomplete
Autocomplete a partial address or place name with Radar. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
autocompleteSAFETY BOUNDARY
Operate Radar with explicit limits
- Authorize Radar with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Radar 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 Radar rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Radar task completed successfully.
CONNECTION MODEL
API key
Radar API key sent in the Authorization header. Find publishable and secret API keys on the Radar Settings page: https://dashboard.radar.com/settings
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
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
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 Radar.