Radar
for LuumenAI
Check geofences, trips, and beacons, then make the location change under review
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.
The Radar toolbox
37 tools: 22 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadAutocomplete Address or PlaceAutocomplete partial addresses and place names based on relevance and proximity.
- ReadForward GeocodeConvert an address into geographic coordinates.
- ReadGet BeaconRetrieve a beacon by Radar _id.
- ReadGet Beacon By TagGet a specific beacon by tag and external ID.
- ReadGet Context for LocationRetrieve context for a given location.
- ReadGet GeofenceRetrieve a geofence by Radar _id or tag/externalId.
- ReadGet Places SettingsRetrieve current Places settings for your Radar project.
- ReadGet Route DirectionsGet turn-by-turn directions between multiple locations.
- ReadGet Route MatrixCalculate travel distance and duration between multiple origins and destinations for up to 625 routes.
- ReadGet TripRetrieve a trip by ID or externalId.
- ReadGet UserGet a user by Radar _id, userId, or deviceId.
- ReadGet Users in GeofenceRetrieve users currently within a specific geofence.
- ReadIP GeocodeGeocode an IP address to city, state, and country.
- ReadList EventsList events.
- ReadList GeofencesList all geofences sorted by updated time.
- ReadList TripsList all trips, sorted by updated time.
- ReadList UsersList Radar users sorted by update time.
- ReadReverse GeocodeConvert geographic coordinates to structured addresses.
- ReadRoute DistanceCompute distance and travel time between origins and destinations.
- ReadSearch GeofencesSearch for geofences near a given location.
- ReadSearch Places Near LocationSearch for places near given coordinates.
- ReadSearch Users Near LocationSearch for users near a location.
- WriteCreate BeaconCreate a new beacon in Radar. Approval by default
- WriteCreate TripCreate a new trip. Approval by default
- WriteDelete BeaconDelete a beacon by its Radar ID. Approval by default
- WriteDelete GeofenceDelete a geofence by ID. Approval by default
- WriteDelete Geofence By TagDelete a geofence by tag and external ID. Approval by default
- WriteDelete TripDelete a trip by its Radar ID or external ID. Approval by default
- WriteDelete UserDelete a user by Radar _id, userId, or deviceId. Approval by default
- WriteTrack Location UpdateTrack a user's location update. Approval by default
- WriteUpdate Places SettingsUpdate Places settings for your Radar project including chain metadata preferences. Approval by default
- WriteUpdate TripUpdate a trip. Approval by default
- WriteUpdate Trip By IDUpdate a trip status by Radar _id or external ID. Approval by default
- WriteUpsert Beacon by IDCreate or update a beacon by Radar _id. Approval by default
- WriteUpsert Beacon by TagCreate or update a beacon by tag and externalId. Approval by default
- WriteUpsert GeofenceCreate or update a geofence by tag and externalId. Approval by default
- WriteUpsert Geofence By IDCreate or update a geofence by Radar _id. Approval by default
One prompt, start to finish
What a governed Radar run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create beacon, create trip, delete beacon, delete geofence, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Radar — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Radar to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.