Get started

Radar for AI agents

Radar is a location infrastructure platform offering geofencing, tracking, geocoding, and routing through one API. Product teams use it to add location-aware features to apps. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect RadarSee the 37 actions ↓
Developer toolsAPI keyMCP + RESTradar.com
AUDIT LOG · RADARPOLICY: acme-support
09:41:07 · claude · u_8f2read
radar.list_trips
List Trips✓ allowed · 212ms
09:41:08 · claude · u_8f2read
radar.get_trip
Get Trip✓ allowed · 164ms
09:41:09 · claude · u_8f2write
radar.create_trip
Create Trip✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
radar.delete_trip
Delete Trip✕ blocked · policy: deny
EVERY RADAR CALL, ON THE RECORD
01 · USE CASES

What agents do in Radar.

01

Geocode an address

Convert a customer address into coordinates to plot on a delivery map.

02

Check users in a geofence read-only

List users currently inside a geofence without sending any notification.

03

Delete a geofence with approval

Remove a geofence only after confirming it is no longer part of an active campaign.

02 · ACTIONS

37 Radar actions, graded by risk.

Every Radar action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

18

Look things up. Allowed by default.

  • radar.get_trip
    Get Trip
  • radar.get_user
    Get User
  • radar.get_beacon
    Get Beacon
  • radar.list_trips
    List Trips
  • radar.list_users
    List Users
  • radar.list_events
    List Events
  • radar.get_geofence
    Get Geofence
  • radar.list_geofences
    List Geofences
  • radar.get_route_matrix
    Get Route Matrix
  • radar.get_beacon_by_tag
    Get Beacon By Tag
  • radar.get_places_settings
    Get Places Settings
  • radar.get_route_directions
    Get Route Directions
  • radar.get_users_in_geofence
    Get Users in Geofence
  • radar.get_context_for_location
    Get Context for Location
  • radar.search_users_near_location
    Search Users Near Location
  • radar.search_places_near_location
    Search Places Near Location
+ 2 MORE

write

14

Create and change things. Allow, or ask the user first.

  • radar.create_trip
    Create Trip
  • radar.update_trip
    Update Trip
  • radar.create_beacon
    Create Beacon
  • radar.update_trip_by_id
    Update Trip By ID
  • radar.update_places_settings
    Update Places Settings
  • radar.ip_geocode
    IP Geocode
  • radar.route_distance
    Route Distance
  • radar.forward_geocode
    Forward Geocode
  • radar.reverse_geocode
    Reverse Geocode
  • radar.upsert_geofence
    Upsert Geofence
  • radar.upsert_beacon_by_id
    Upsert Beacon by ID
  • radar.upsert_beacon_by_tag
    Upsert Beacon by Tag
  • radar.upsert_geofence_by_id
    Upsert Geofence By ID
  • radar.autocomplete_address_or_place
    Autocomplete Address or Place

destructive

5

Delete, cancel or archive. Ask first, or deny outright.

  • radar.delete_trip
    Delete Trip
  • radar.delete_user
    Delete User
  • radar.delete_beacon
    Delete Beacon
  • radar.delete_geofence
    Delete Geofence
  • radar.delete_geofence_by_tag
    Delete Geofence By Tag
03 · HOW IT WORKS

Radar in three steps.

  1. 01Your users connect RadarThey add their Radar api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Trip” can wait for the user, and “delete Trip” can be denied outright.
  3. 03Any agent can actYour agent calls Radar through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('radar', {
  read: 'allow',
  write: 'ask',        // create_trip
  destructive: 'deny',  // delete_trip
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Radar connects.

Users add their Radar api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Radar connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Radar from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Radar and Arc0, answered.

Q01

Can I use Radar with Claude, ChatGPT or Cursor?

Yes. Connect Radar to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Radar actions you allow.

Q02

How do users connect Radar?

Users add their Radar api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Radar actions can my agent take?

37 in total: 18 read, 14 write and 5 destructive, such as “create Trip”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Radar?

Yes. Actions like “delete Trip” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Radar too?

Yes. The same Radar connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Radar into your agent.

Your users connect Radar once, under your brand. Your agent gets 37 actions behind your policies, with every call on the record.

Connect RadarBrowse all apps →

Free to build · MCP + REST · Audit log on every plan