The map app
A web map in the browser with a chat panel beside it. People ask questions in plain language and get answers as tables, charts, record cards and changes on the map.
Chat bridges for maps and work data
Black Marlin Labs builds bridges that connect AI assistants to your maps, asset records and work-management data. Crews, dispatchers and managers ask a question and get the answer as a table, a chart, a report or a change on the map.
The demo is public and needs no sign-in.
What the bridges are
A bridge gives an AI assistant a short, defined list of things it is allowed to do with your data, and nothing else.
A web map in the browser with a chat panel beside it. People ask questions in plain language and get answers as tables, charts, record cards and changes on the map.
A small service between the app and the AI model. It gives the assistant a fixed set of tools (find features, query work records, run a report, draft an update) and checks who is signed in before any of them run.
Map layers, asset records, work orders and other business data, read and written in place through scoped service accounts. The bridge does not keep its own copy of your records.
Bridges use the Model Context Protocol (MCP), an open standard for connecting AI assistants to tools. Adding a new system means adding its tools, not rebuilding the app.
How they can be used
Each app is set up for the people using it, from a field crew working their own list to a dispatcher watching every crew at once.
See today’s work near you, open the full record from the map, and update status with a confirm step before anything is saved.
“What’s on my list this week, closest first?”
Find the backlog, create and reassign work, and catch possible duplicates nearby before a new request is logged.
“Show overdue work by crew and priority.”
Charts, KPI tiles and tables on request, plus a shared report library so the same question gets the same report every time. Export to PDF or CSV.
“Run the monthly summary for the north district.”
Filter and color layers, zoom to features, measure distances, find the nearest assets and drop points on the map without hunting through menus.
“Color open requests red and zoom to them.”
Log a problem at a spot on the map even before the asset is known. A dispatcher can attach the asset or create related work later.
“Log a request here: blocked storm drain.”
Combine map features with records from other systems in one answer, so people stop switching between apps to piece it together.
“Which customer complaints are near open work?”
Works with what you have
Bridges sit on top of the systems you already run. Nothing needs to be migrated first.
Assets, inspections, work orders and service requests, read and updated through each system’s own API or database.
Contacts, cases and customer-reported issues, tied back to the map location and the work they created.
Hosted and on-premises map services and web maps, with your existing sharing and sign-in.
Work-management and reporting databases, through read-only logins by default and a separate login for approved writes.
Where your data lives
Maps stay in your GIS. Work and asset records stay in your databases and business systems. The bridges query them live.
Our hosted environment for evaluation, your own cloud account, or on-premises next to your servers.
Use your own AI provider key, so usage and data terms are between you and your provider. Admins choose the models.
Only chat history and generated report files, per user, in the deployment you choose.
See it working
A public replay of a field and dispatch app for water-quality sampling and site inspections on Cape Cod. Step through a recorded chat, open records, run charts and use the map tools. Nothing to install, and no sign-in.
The chat answers are recorded, and the work data is fictional.
Get access
The live apps are in early testing with a small group. Send an email with your name, your organization and what you would like to try, and you will hear back about access.
Already have access? Sign in to the apps.