Use Radar from Claude
Add the Radar connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Radar connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Radar connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Radar connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
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.
Connect Radar once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Ask the agent to autocomplete a partial address so a form submission resolves to a verified, standard address.
Autocomplete this partial address a customer entered using Radar: 123 Main near downtown Austin.
Have the agent create a trip with origin and destination details so progress can be tracked from dispatch to arrival.
Create a Radar trip from our warehouse to this customer address for today's delivery.
Get the agent to add a beacon device so a new site can support indoor location triggers.
Create a Radar beacon for the new store location so we can trigger check-in alerts.
Suggests addresses or place names based on a partial input and optional location bias.
Registers a physical beacon device for indoor location tracking.
Starts tracking a trip given origin and destination details.
Removes a beacon from Radar using its unique identifier.
Removes a geofence from Radar using its unique identifier.
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.
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.
Radar uses publishable and secret API keys. An admin adds these once when creating the connection and chooses which Spaces can use it.
Yes. A Radar prompt can become a type.com automation, such as a daily summary of active trips, posted to an operations channel.
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.
Connect Prismic to Claude in type.com to search documents, query content, and review custom types from a thread.
Connect Procfu to Claude in type.com to compare data arrays and move files out of Podio as part of a larger automation.
Connect Ragic to Claude in type.com to look up records, download files, and generate reports from a shared thread.
Connect Ragie to Claude in type.com to ingest documents, pull in web content, and define extraction instructions for your knowledge base.