Skip to main content
Always-on assistants keep running when you are not chatting. They live in your messaging apps, run tasks on a schedule, and message you when something changes. Muse, Grok Bot, Instinct and dots are examples. Connected to Ploti, they answer from the official parcel, zoning, permit and ordinance records Ploti holds for your coverage areas, the counties you pick and pay for. Most are set up with one chat message that links to Ploti’s setup instructions. The assistant reads them and installs what it needs. From then on it reaches Ploti’s records through the command-line tool or web API, with a key you make.

​
Set up with one message

Muse

One message, then Ploti’s command-line tool and API

Grok Bot

One message, then Ploti’s command-line tool and API

Instinct

One message, then Ploti’s command-line tool and API

dots

One message, then Ploti’s command-line tool and API
Each setup follows the same steps:
  1. Open Connect your assistant in Ploti, choose the assistant and make a key.
  2. Send the assistant the setup message.
  3. When it asks for the key, add it in the assistant’s settings, not in the chat.

​
An agent you run yourself

A bot you build and run on your own server uses the command-line tool or the Python library with an API key. It might watch for new permits or answer your team’s questions in chat. Your own agent covers it.

​
Any other assistant

An assistant that can fetch a web page and keep a secret can follow the same setup message. One that supports MCP connectors can use Ploti’s connector instead; see Chat assistants. An always-on assistant can also put what it finds on a Ploti map and send you the link. Show results on a map explains how, including the CLI commands for assistants that use only the command-line tool.