---
title: "Radar integration for LuumenAI"
url: "https://www.luumen.ai/integrations/radar/"
entity: SoftwareIntegration
category: "Source control & CI/CD"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Radar integration for LuumenAI

Check geofences, trips, and beacons, then make the location change under review

## What LuumenAI can do with Radar

LuumenAI connects to Radar with an API token and exposes 37 tools (22 read-only · 10 write · 5 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 37 tools (22 read-only · 10 write · 5 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Source control & CI/CD

## About Radar with LuumenAI

Radar holds the geofences, trips, beacons, and user records behind your location features. Luumen reads all of it on request: who is inside a geofence right now, what a trip's current status is, how a route resolves. When something needs to change — a trip marked complete, a beacon added, Places settings adjusted — the change is previewed and sent for approval first. Luumen authenticates with an API key.

## Example tools

Read-only (22 in total):

- `RADAR_AUTOCOMPLETE_ADDRESS_OR_PLACE` — Autocomplete partial addresses and place names based on relevance and proximity.
- `RADAR_FORWARD_GEOCODE` — Convert an address into geographic coordinates.
- `RADAR_GET_BEACON` — Retrieve a beacon by Radar _id.
- `RADAR_GET_BEACON_BY_TAG` — Get a specific beacon by tag and external ID.
- `RADAR_GET_CONTEXT_FOR_LOCATION` — Retrieve context for a given location.
- `RADAR_GET_GEOFENCE` — Retrieve a geofence by Radar _id or tag/externalId.
- `RADAR_GET_PLACES_SETTINGS` — Retrieve current Places settings for your Radar project.
- `RADAR_GET_ROUTE_DIRECTIONS` — Get turn-by-turn directions between multiple locations.

Write and destructive (15 in total, subject to configured approval policy):

- `RADAR_CREATE_BEACON` — Create a new beacon in Radar.
- `RADAR_CREATE_TRIP` — Create a new trip.
- `RADAR_DELETE_BEACON` — Delete a beacon by its Radar ID.
- `RADAR_DELETE_GEOFENCE` — Delete a geofence by ID.
- `RADAR_DELETE_GEOFENCE_BY_TAG` — Delete a geofence by tag and external ID.
- `RADAR_DELETE_TRIP` — Delete a trip by its Radar ID or external ID.
- `RADAR_DELETE_USER` — Delete a user by Radar _id, userId, or deviceId.
- `RADAR_TRACK_LOCATION_UPDATE` — Track a user's location update.

## Frequently asked questions

### How does LuumenAI connect to Radar?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Radar on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to Radar — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/radar/