Radar logo
ConnectorRadar

Radar integration for Claude and Codex

Connect Radar once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Radar from Claude

Add the Radar connection to a Space that runs Claude, then use it from every channel in that Space.

Use Radar from Codex

Add the Radar connection to a Space that runs Codex, then use it from every channel in that Space.

Use Radar from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Developer Tools & IT

What the Radar connector can do

Radar provides location infrastructure for geocoding, geofencing, and trip tracking used in logistics and field apps. With a Radar connection in type.com, the agent can autocomplete a partial address during intake, start tracking a new trip from origin to destination, or register a physical beacon for indoor location tracking, so location-based workflows run from the same thread as the rest of an operations plan.

One connection, many Spaces

Connect Radar once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with Radar in type.com

Clean up an address during intake

Ask the agent to autocomplete a partial address so a form submission resolves to a verified, standard address.

Try asking
Autocomplete this partial address a customer entered using Radar: 123 Main near downtown Austin.

Start tracking a delivery trip

Have the agent create a trip with origin and destination details so progress can be tracked from dispatch to arrival.

Try asking
Create a Radar trip from our warehouse to this customer address for today's delivery.

Register a beacon for a new location

Get the agent to add a beacon device so a new site can support indoor location triggers.

Try asking
Create a Radar beacon for the new store location so we can trigger check-in alerts.

Representative actions

  • Autocomplete Address or Place

    Suggests addresses or place names based on a partial input and optional location bias.

  • Create Beacon

    Registers a physical beacon device for indoor location tracking.

  • Create Trip

    Starts tracking a trip given origin and destination details.

  • Delete Beacon

    Removes a beacon from Radar using its unique identifier.

  • Delete Geofence

    Removes a geofence from Radar using its unique identifier.

Connection

API and auth details

Radar provides location infrastructure APIs and SDKs for geofencing, trip tracking, routing, geocoding, search, maps, and location context. Integrations can manage users, geofences, trips, events, places, contexts, routes, regions, and location-triggered automation with publishable and secret API keys.

FAQ

Questions people ask before connecting Radar

Can Claude manage Radar location data from type.com?

Yes. With a Radar connection shared to a Space, the agent can autocomplete addresses, track trips, and manage beacons and geofences in any thread, visible to the whole team.

How does type.com authenticate with Radar?

Radar uses publishable and secret API keys. An admin adds these once when creating the connection and chooses which Spaces can use it.

Can trip tracking updates run automatically?

Yes. A Radar prompt can become a type.com automation, such as a daily summary of active trips, posted to an operations channel.

Is this the same as an MCP server for Radar?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More developer tools & it connectors

All Developer Tools & IT integrations