Radar

@Radar what geofences and places are near 37.7749, -122.4194? I need context for this location to understand what's around our SF office.

Based on the coordinates 37.7749, -122.4194 (San Francisco), this location falls within 2 active geofences: 'downtown-sf-zone' (radius 500m) and 'market-street-corridor' (polygon boundary). Nearby places include Civic Center Plaza (0.3km), UN Plaza (0.4km), and several transit stations. The region context shows this is in San Francisco County, California, US, postal code 94102. This data reflects your account's current geofence configuration and Radar's place database as of this query.

This example shows Radar's core location intelligence — combining your custom geofences with Radar's place data. Requires valid lat/long input and an API key with geofence read permissions. The geofences returned depend entirely on what you've previously created in your Radar project; this is illustrative output.

@Radar create a trip from 123 Main St, Austin TX to 456 Oak Ave, Dallas TX with external ID 'delivery-order-7821' so we can track this route in real-time.

Trip created successfully with Radar ID `trip_abc123xyz`. Origin geocoded to 30.2672, -97.7431 (Austin) and destination to 32.7767, -96.7970 (Dallas). External ID 'delivery-order-7821' attached for your reference. The trip is now live and will generate location updates as the device moves along the route. Estimated distance: 195 miles. You can query trip status or delete it using the Radar ID or your external ID.

This demonstrates Radar's trip tracking workflow — geocoding addresses, creating the trip object, and returning identifiers for ongoing monitoring. Requires API key with trip write permissions. The trip persists in Radar's system until explicitly deleted or completed; be mindful of active trip quotas on your plan.

@Radar I'm typing '1600 Pennsylv' — autocomplete this address and tell me the top 3 suggestions so I can pick the right one for our DC event venue search.

Top 3 autocomplete suggestions for '1600 Pennsylv': (1) 1600 Pennsylvania Avenue NW, Washington, DC 20500 (The White House), (2) 1600 Pennsylvania Avenue SE, Washington, DC 20003 (residential area), (3) 1600 Pennsylvania Street, Denver, CO 80203. Each result includes full formatted address and coordinates. The ranking prioritizes relevance and proximity if you pass a bias location. This is a partial match query — results improve as the user types more characters.

Showcases Radar's autocomplete for address entry UX — useful in forms or search interfaces where users type incrementally. Requires API key with geocoding permissions. Autocomplete is rate-limited (check your plan); results vary by query specificity and optional location bias. This example illustrates typical output structure, not a live query.

When Radar wins for same-day service territory checks

A 6-person HVAC dispatch team runs 15-20 calls a day across three metro zones. They need to know if a new service request falls inside their coverage geofences and which tech is closest. Radar's Get Context for Location and geofence tools answer both questions in one call—no manual map checking, no spreadsheet lookups. The team creates geofences for each territory, then uses Forward Geocode to turn customer addresses into coordinates and Get Context to match them to zones and nearby techs. This works cleanly when your service area has stable boundaries and you're making under 10k lookups a month. If your zones shift weekly or you're routing 50+ techs, you'll hit the API rate limit and need a heavier GIS stack. For small field teams with fixed territories, Radar keeps dispatch decisions fast and removes the guesswork.

When trip tracking fits courier handoff workflows

A 3-person logistics startup coordinates handoffs between warehouse packers and gig couriers for same-day grocery delivery. They need to know when a courier arrives at the warehouse and when they leave for the customer. Radar's Create Trip and trip lifecycle tools let them track each leg without building GPS polling from scratch. The warehouse app calls Create Trip when a courier accepts an order, Radar pings the backend when the courier enters the pickup geofence, and the customer gets an ETA update when the trip starts moving toward delivery. This setup works when you're doing under 500 deliveries a day and your couriers use a single app. If you're coordinating multi-modal handoffs or need sub-minute location updates, Radar's trip abstraction gets too coarse. For early-stage delivery ops with straightforward pickup-to-dropoff flows, it's the fastest way to add live tracking without a geospatial engineering hire.

When Radar's autocomplete beats rolling your own

A 10-store regional retail chain wants a store locator on their site that suggests locations as customers type. They need autocomplete that biases results toward their operating region and doesn't send users to competitors. Radar's Autocomplete Address or Place tool returns ranked suggestions with proximity bias, so a customer typing 'Main St' in Portland sees the Portland store first, not the one in Seattle. The team wires it to their storefront search bar and uses Forward Geocode to snap the final selection to coordinates for distance sorting. This works when you have under 50 locations and your customers are searching within a known region. If you're a national chain with 500+ stores or need to filter by real-time inventory, you'll want a full Places API with custom ranking. For regional retailers who need fast, relevant autocomplete without maintaining a geocoding pipeline, Radar's tooling is the right scope.