View as Markdown

Privacy and limits

What the agent can do, what it can't, and what to keep out of a map.

What the agent can do

  • Create a map from place names, coordinates, GeoJSON or area data you give it (or that it finds).
  • Read the editable body of any map it has the link to.
  • Change a map it created, as long as it still has the edit token.

What it can't do

  • Read your files, accounts or location. The server only sees what the agent sends in a tool call.
  • Delete maps. They expire on their own.
  • Change a map without its edit token. It cannot modify maps made by someone else.
  • Make a private map. There is no sign-in and no access control.

Maps are public by link

Anyone who has a map's link can open it. Map IDs are 10 random characters and can't be guessed, and map pages are marked noindex so search engines skip them, but a link posted in public is public. Don't put data on a map that you wouldn't share with whoever receives the link. Place names you ask the agent to look up are sent to the geocoding service (Photon); routes use FOSSGIS OSRM.

The edit token is a secret

Creating a map returns an edit_token and an edit_url once. Whoever has either can change that map. The agent keeps the token in the conversation so it can update the map on request; share only the normal map link, not the edit link or token, and tell the agent not to post them. Wrong or missing tokens are rejected.

Expiry and limits

  • A map is deleted after 30 days without views. Each view or update restarts the clock.
  • No account and no API key. Creation is limited to 60 maps per minute per IP.
  • Up to 50 places per request and 2 MB per body.

For the full list see limits and data lifetime in the API docs.

Next steps