ceven

Radar

Syncs location events and geofence triggers into your operational workflows, automates user tracking updates, and converts coordinates into readable addresses for your team.

Try Radar in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Radar integration

    • Describe the outcome and Ceven picks the right Radar calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Radar data, across all 37 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Radar access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Radar, when, and on whose behalf.
    • The agent pauses and asks when Radar is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Radar.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Radar action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Radar, and when to use it.

Forward Geocode
Use this when you have a full address string and need precise latitude and longitude coordinates for mapping.
Reverse Geocode
Convert geographic coordinates into a structured human readable address for reports or notifications.
Upsert Geofence
Create a new geofence or update an existing one using a tag and external id.
Get Context for Location
Pull geofences, place, and region information for a specific set of coordinates.
Search Users Near Location
Retrieve a list of users within a specified radius of a given location.
Track Location Update
Send a location update for a user to trigger events or update their current position.
Create Trip
Start tracking a new trip after gathering the origin and destination details.
Update Trip
Modify the mode, destination, schedule, or active status of an existing trip.
Get Users in Geofence
List all users currently inside a specific geofence using its tag and external id.
Route Distance
Compute the distance and travel time between origins and destinations for timing estimates.
Search Geofences
Find all configured geofences within a specific radius of given coordinates.
IP Geocode
Determine the city, state, and country associated with a specific ip address.
List Events
Pull a paginated list of location events with optional filters for analysis.
Autocomplete Place
Get address suggestions based on a partial input string and user proximity.
Autocomplete Address or Place
Tool to autocomplete partial addresses and place names based on relevance and proximity. use after a user inputs a partial address/place to get suggestions, optionally biased by location.
Delete Geofence
Tool to delete a geofence by id. use when supplying a geofence’s unique identifier to remove it.
Delete Trip
Tool to delete a trip by its radar id or external id. use after confirming the trip exists.
Get Geofence
Tool to retrieve a geofence by radar id or tag/externalid. use when you need to fetch full details of an existing geofence.
Get Places Settings
Tool to retrieve current places settings for your radar project. use when you need to inspect chain detection, supported countries, external id requirements, and other places metadata.
Get Trip
Tool to retrieve a trip by id or externalid. use when you have a trip id or externalid to fetch its details.
List Beacons
Tool to list all beacons sorted by creation date. use when you need an overview of all configured beacons.
List Geofences
Tool to list all geofences sorted by updated time. use when you need an overview of all configured geofences.
List Trips
Tool to list all trips, sorted by updated time. use when you need to page through the latest trips.
List Users
Tool to list radar users sorted by update time. use when you need to page through users in your project.
Search Places Near Location
Tool to search for places near given coordinates. use when you need to find points of interest around a location.

25 actions · scroll to see them all

Frequently asked questions

Ceven connects to Radar via webhooks to receive instant notifications when a user enters or exits a defined geofence. When Radar fires an event, Ceven captures the user id and geofence tag, then matches them against your workflow rules. For example, if a user enters a high priority zone, Ceven can immediately trigger a Slack alert or update a row in your database. This happens in real time without the agent needing to poll the Radar API constantly, ensuring that your business logic executes the moment the physical event occurs in the real world.
Yes, you can use the Track Location Update action to manually push coordinates into Radar. This is ideal for hardware devices or third party telematics systems that send raw latitude and longitude data. Ceven acts as the bridge, taking the incoming data stream from your hardware and pushing it into Radar to leverage their geofencing and trip logic. Once the data is in Radar, Ceven can then run any of the subsequent workflows based on the location intelligence provided by the Radar platform.
Forward geocoding is the process of taking a written address, like 123 Main Street, and turning it into a pair of coordinates that a computer can map. Reverse geocoding does the opposite by taking a latitude and longitude and returning a human readable address. In Ceven, you use Forward Geocoding when you need to set up a new geofence based on a customer address. You use Reverse Geocoding when you want to send a confirmation email to a user telling them exactly which street corner they are currently standing on.
Radar imposes specific limits on the number of geofences based on your plan tier. For most users, this is a high ceiling, but enterprise accounts with millions of dynamic geofences should be aware that API rate limits apply to the Upsert Geofence endpoint. If you attempt to sync a massive database of locations in one burst, Radar may return a 429 Too Many Requests error. Ceven handles this by implementing an exponential backoff strategy, queuing the requests and retrying them automatically to ensure every geofence is eventually created without crashing your workflow.
This action queries the Radar database for any users who have sent a location update within a specific radius of your target coordinates. You provide the center point and the distance in meters. Radar returns a list of matching users, which Ceven can then loop through to perform further actions. This is commonly used for proximity marketing or finding the closest driver to a pickup point. Note that this only returns users who have an active tracking session or a recent location update stored in the Radar system.
Yes, you can build workflows that use the Delete Geofence or Delete Trip actions to maintain your environment. For instance, you can set up a weekly cleanup task where Ceven lists all trips that are marked as completed and older than thirty days, then iterates through that list to delete them from Radar. This keeps your Radar dashboard clean and ensures you are not hitting storage limits or paying for unnecessary data retention on your Radar plan.
Ceven does not maintain its own database of your users live coordinates. Instead, it queries Radar in real time or reacts to events sent by Radar. When you ask an agent to find a user, it makes a request to Radar, receives the current location, and uses it to complete the task. Your location data remains secured within the Radar infrastructure, and Ceven only accesses it temporarily to execute the specific logic defined in your workflow.
IP geocoding provides a general estimate of a users location based on their network provider and is typically accurate to the city or region level. It cannot provide the exact street address or precise coordinates like GPS based tracking can. In Ceven, IP geocoding is best used for coarse location tasks, such as determining which regional server to route a user to or identifying the country of origin for a web request to prevent fraud, rather than for precise geofencing.

Alternatives to Radar

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Google Maps Platform logoGoogle Maps PlatformMapbox logoMapboxHere Technologies logoHere Technologies

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Radar and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free