Research
Your sites, in your own AI, compared with Esri's announcement

White Paper
Overview
AI Connections lets you connect the AI app you already use to Omniris. It can then answer from your own sites, flights, files and findings, measure what changed, download what you need, update a finding, and draft a request for a new flight. It acts as you, it sees only what you can see, and everything it does is recorded.
Read MoreYour sites, in your own AI, compared with Esri's announcement
AI Connections lets you connect the AI app you already use to Omniris. It can then answer from your own sites, flights, files and findings, measure what changed, download what you need, update a finding, and draft a request for a new flight. It acts as you, it sees only what you can see, and everything it does is recorded.
Summary
People now do a large part of their work inside an AI app: writing the weekly report, preparing for a site meeting, answering a client's question. Until that app can reach the drone data, someone still has to open Omniris, find the right flight, read off the numbers and paste them across.
AI Connections removes that step. Omniris speaks the Model Context Protocol (MCP), the open standard AI apps use to reach other systems. You give your AI app one address, sign in to Omniris, and choose what the connection may do. From then on the AI app can work with your Omniris data directly, using the same tools that Orion, the assistant built into Omniris, uses.
Your own data
Your sites, flights, maps, 3D surveys, thermal and multispectral flights, files and findings. Not a general map of the world: the places you fly.
Real measurements
Volumes, elevation profiles, temperatures inside an area, what changed between two flights. Worked out from your surveys, with the picture to show it.
It can act, carefully
Update and comment on findings, start a change trace, draft a request for a new flight. You choose whether a connection may change anything at all.
It acts as you
A connection sees exactly what you can see in Omniris. Never more. Another customer's data is out of its reach, whatever is asked.
Everything is recorded
Every tool call is listed in the connection's Activity. A changed finding says who changed it and through which connection.
Runs where Omniris runs
In the cloud, in the data center edition, and inside your own on-premises site. On your own site, the AI app talks to your own server.
Included
Part of every plan and every edition. There is nothing extra to buy and no developer account to open.
What an AI connection is
A connection is a standing permission for one AI app, or one script, to use Omniris as one person. It has a name you give it, one of two levels of access, and a record of what it has done. You can revoke it at any moment.
| Kind | For | How it signs in |
|---|---|---|
| An AI app | Claude, Microsoft Copilot, Cursor and other apps that support MCP, in the browser, on the desktop or in a code editor | The app sends you to Omniris. You sign in the way you always do and approve the connection on a page that says exactly what is being asked. |
| A personal token | A script, a scheduled report, an agent that runs without a person at the keyboard | You make a token in Omniris and give it to the script. The token is shown once. |
Each connection has one of two levels of access, and you choose it, not the AI app:
- Read. See what you can see, run measurements and comparisons, and download files.
- Read and change. Also update and comment on findings, start change traces, export traces, and draft job requests.
How to connect
An AI app
- In Omniris, open Account and choose AI Connections. Copy the address shown at the top.
- In your AI app, add that address as a custom connector. Some apps call it an MCP server.
- The app sends you to Omniris. Sign in if you are asked to.
- Omniris shows which app is asking, and that it will act as you. Choose Read or Read and change, give the connection a name, and press Allow.
- Ask your first question.
There is no key to copy and nothing to install. If you use the same AI app on a second computer, it signs in there separately, and the connection shows how many of your devices it is signed in on.
A script
- On the same tab, press New token.
- Give it a name and choose Read or Read and change.
- Copy the token. It is shown once. If it is lost, revoke it and make another.
- Your script sends the token with each request to the address on the tab.
Before you press Allow, Omniris names the app, says where you will be sent back to, and warns you when it cannot verify the app's name or when the app runs on your own computer. An administrator is told plainly that the connection will have administrator access. Consent is asked every time an app connects, never assumed.
What you can ask for
Ask your AI app the way you would ask a colleague who knows your sites. A few examples:
| You ask | What happens |
|---|---|
| "What changed at the north yard since the last flight?" | The two flights are compared and the changed areas come back numbered on the photo map, each with its size. |
| "How much material is in stockpile 3, and how does that compare with last month?" | The volume is measured inside the saved boundary on each survey, with the difference between them. |
| "Where is the hottest part of the roof on Tuesday's thermal flight?" | The temperatures inside the area are read from the flight's temperature map, in °F and °C, with the picture. |
| "List the open findings on the substation, most severe first." | The findings you can see, with their status, severity, category and who they are assigned to. |
| "Mark F-000412 as confirmed and note that the crew is booked for Friday." | With Read and change: the status is changed and the comment added, both recorded under the connection's name. |
| "Send me the orthomosaic from the June flight." | A download link for that file, good for one use. |
| "We need the east slope flown again. Draft the request." | With Read and change: a draft job with the area outlined, waiting for you under Jobs. |
| "Write this week's site report." | Your AI app gathers the flights, changes, measurements and findings it needs, and writes the report in its own window, alongside whatever else it has open. |
The last row is the point. The AI app can combine Omniris with everything else it is connected to: your documents, your mail, your project schedule. Omniris supplies the part nobody else has, which is what is actually on the ground.
The tools a connection has
A connection is offered the tools the person behind it may use. They are the same tools Orion uses inside Omniris, so an answer through your AI app and an answer from Orion come from the same measurement.
| Area | What the tools do | Access needed |
|---|---|---|
| Your records | List what can be looked up, describe it, and look it up: jobs, files and folders, sites, processing runs, measurements, schedules and the rest of what you can open | Read |
| Findings | List findings, open one, read its history | Read |
| Findings | Change a finding's status, severity, category or assignee; add a comment | Read and change |
| Surveys and imagery | Heights from a 3D survey, a thermal summary, areas of a field that match a condition, a close look at a place on the map | Read |
| Measurements | Compare two flights, measure a volume, compare a volume across dates, temperatures inside an area, an elevation profile | Read |
| Site changes | Show the changed areas of a site | Read |
| Site changes | Start a change trace, find unusual changes, describe the changed areas, export traces | Read and change |
| Files | A download link for one file | Read |
| New flights | Draft a job request over areas you outline | Read and change |
| Weather and places | Flyability forecast, current aviation weather, finding an address | Read |
| Processing problems | Why a processing run failed, and its log | Read, administrators only |
Pictures come back as pictures: a changed-areas map or a temperature view arrives in your AI app as an image it can show you and describe. A feature your site does not use is simply not offered.
Acting as you, and no further
The rule is one sentence: a connection sees and does exactly what its person can see and do in Omniris. The same organizations, the same shared folders, the same job folders, the same role. It is not a separate account with its own permissions to keep in step, so there is nothing to drift.
- Checked on every request. If your access to a folder is removed this morning, the connection has lost it this morning.
- Your level of access, your choice. A Read connection cannot change anything. If an AI app asks a Read connection to change a finding, Omniris refuses and says the connection would need Read and change.
- A token that works in one place. A connection's token opens the AI connection and nothing else in Omniris. It cannot sign in to the app, and it can never list, make or revoke connections.
- Nothing secret is stored. Omniris keeps only a scrambled fingerprint of each token. A token cannot be read back out of Omniris, by anyone.
- Deactivated means stopped. When an account is deactivated or deleted, its connections stop for good. A billing lock stops them until the lock is lifted.
- Pilots, clients, managers and administrators each get the tools their role has in the app. A pilot's job request is a job of their own; a client's is a request to the marketplace.
File names, finding descriptions, comments and logs are written by people. Omniris tells every connected AI app that such text is data to be read, not instructions to follow. And because a connection can never do more than its person and its level of access allow, a misled AI app is still held inside those limits.
Changes, drafts and downloads
Changing a finding
A change names the version of the finding it was based on. If someone else changed the finding in the meantime, nothing is overwritten: the AI app is given the finding as it now stands and tries again. Every change and comment is recorded in the finding's History as you, with the connection's name beside it.
Drafting a request for a new flight
When the data you need does not exist yet, the AI app can prepare the request to capture it: the areas to fly, the areas to stay out of, what you want delivered and when. Omniris creates a draft.
- Nothing is sent to pilots and nothing is charged.
- The draft waits under Jobs. You open it, check it, and submit it yourself.
- A connection can never submit, assign or price a job.
- If the AI app repeats the same request, you get the same draft back, not a second one.
Downloading a file
The AI app asks for a file and receives a link. The link works once, for two minutes, and the download is written into the file's custody record when the file is actually fetched.
A file you have protected with encryption is delivered still encrypted. An AI connection is never handed a protected file in the clear. To use the file decrypted, download it in Omniris, where the usual checks apply. See Security, encryption and data control.
Credits and usage
Anything that costs credits or counts against your plan in Omniris costs the same when a connection does it, on the same account, and is refused in the same words when the account has reached its limit. A connection is not a way around a limit, and not a second bill.
What is recorded
| What happened | Where you see it |
|---|---|
| Every tool call | The connection's Activity: when, which tool, whether it worked, how long it took. Kept for a year. |
| A finding changed or commented on | The finding's History: your name, "via" the connection's name. |
| A file downloaded | The file's custody record, marked as a download through an AI connection. A protected file is marked as delivered encrypted. |
| A change trace started or exported | The custody record of the site's files, marked as started through an AI connection. |
| A job drafted | The draft itself, under Jobs. |
The Activity list shows what a connection did, not the contents of the questions and answers, which stay in your AI app. For how the custody record itself is kept and proved, see Evidence you can prove.
Managing your connections
Account → AI Connections lists every connection of yours: its name, the app or token behind it, what it may do, when it was made and last used, and how many of your devices it is signed in on.
- Activity shows what the connection has done.
- Revoke stops the connection on its very next request, on every device. You can connect the app again whenever you like.
- Remove takes a connection that is no longer active off your list. The record of what it did is kept.
- Administrators see a person's connections on that person's page under Settings → Users, and can revoke one. An administrator cannot make a token that acts as someone else.
- On your own site, the administrator's "Sign everyone out" also ends every AI connection signed in before it.
The tab is the same on the web and in the desktop application.
Where it runs
The AI connection is part of Omniris itself, so it is wherever your Omniris is: on Azure, on Google Cloud, in the data center edition, and on your own on-premises site.
| Your Omniris | AI apps that run on a vendor's servers | AI apps and scripts on your own computers |
|---|---|---|
| Cloud or the data center edition | Connect | Connect |
| On-premises, reachable from the internet with a secure address | Connect | Connect |
| On-premises, on your own network only | Stay outside, as your network intends | Connect, without leaving your network |
That last row matters to anyone who keeps their data on their own ground. An AI app running on your own computer talks to your own Omniris server, on your own network. The measurements are worked out on your server. What crosses your network boundary is whatever your AI app sends to its own AI service, which is your choice of AI app to make.
Compared with Esri's announcement
Esri has announced two things for AI agents: the ArcGIS agentic developer toolkit and MCP for ArcGIS Location Services (beta). They are useful, and they are aimed at something different. This section sets out, from Esri's own documentation and blog [1–7], what was announced, and how AI Connections differs.
What Esri announced
- The ArcGIS agentic developer toolkit is, in Esri's words, "a set of tools that helps AI agents perform development tasks with ArcGIS SDKs, APIs, and underlying technologies": agent skills that guide a coding agent through ArcGIS workflows, and a server that gives the agent access to Esri's developer documentation [1]. It helps a developer's AI write ArcGIS code.
- MCP for ArcGIS Location Services (beta) is an Esri-hosted server that gives AI agents Esri's location services: turning an address into coordinates and back, routes and drive-time areas, the elevation at a point, a static map image, statistics about a place such as population, and a buffer around a point [2][3].
The location services server has been available as a beta since June 29, 2026, through Esri's early adopter program [6]. Esri has also described a parallel effort in the same program, MCP support for ArcGIS Enterprise, which "focuses on exposing GIS capabilities from an organization's enterprise deployment", and says the two can be combined in one session [5][7].
How AI Connections differs
| Omniris AI Connections | Esri, as announced | |
|---|---|---|
| Whose data | Yours: your sites, flights, surveys, files and findings | Esri's reference services and developer documentation. The published location services tools answer about addresses, routes, elevation and places in general, which Esri describes as "global, authoritative data"; none of them reads a customer's own maps, layers or imagery [3][7]. An organization's own ArcGIS Enterprise content is the subject of the separate early adopter effort [7] |
| Who it is for | The people who run the sites: owners, managers, inspectors, pilots. No code. | The toolkit is for developers building applications with ArcGIS [1]. The location services server is built by a team that makes "location services for developers", and can also be used from an AI app without writing code [7] |
| What it measures | Volumes, elevation profiles, temperatures and change between dated flights, on your own surveys | The elevation at a point, a route, a drive-time area, a map image [3] |
| What it can change | Findings, change traces and draft job requests, when you allow it | The published tools look things up; none changes a record [3] |
| Getting new data | Drafts the request for a new flight, for you to submit | Not part of the announcement |
| The record | Every call in the connection's Activity; changes in the finding's History; downloads in the custody record | Not described in the documentation reviewed |
| What you need | Your Omniris sign-in. Included in every plan. | An ArcGIS Location Platform account; stored geocoding and the place-statistics tools need pay-as-you-go billing enabled [2][4]. Each use is charged at that service's standard rate [6] |
| Status | Part of the product | The location services server is a beta, and Esri says the way some tools work may still change [2][7] |
Why that matters
- The question that matters is about your site. "Where is 380 New York Street?" has the same answer for everyone. "How much did the stockpile shrink since the last flight?" has an answer only your own surveys can give. AI Connections answers the second kind.
- An answer is only useful if you can act on it. A connection can turn what it found into a confirmed finding, a comment for the crew, or a drafted re-flight, and each of those is recorded.
- It is one sign-in, not a new account. There is no developer account to open, no key to provision and no usage bill to set up. The site manager connects the AI app they already use with the Omniris sign-in they already have.
- It is the same product you already trust with the evidence. The same permissions, the same encryption, the same custody record. Nothing new to secure.
They work together
The two are not alternatives. An AI app can hold both connections at once: Esri's to find an address or plan the drive to a site, and Omniris for everything about the site itself. Esri makes the same point about combining its own servers in one session [7]. Omniris also publishes your maps into your own ArcGIS account, described in Sharing, delivery and integrations.
What the product claims, and what it doesn't
- Drafts, not orders. A connection drafts a job request. Only you submit it.
- Protected files are not decrypted. They are delivered encrypted, or downloaded decrypted in Omniris itself.
- One call at a time finishes before it answers. A measurement that draws a map can take a minute or two. A connection runs up to four tool calls at once, and a fifth is refused until one finishes.
- A started call runs to its end. It cannot be cancelled halfway.
- Download links are short-lived. One use, two minutes. The AI app asks again for a new one.
- Signing in from an AI app needs a secure address. On a site without one, connect with a personal token.
- The tab is on the web and in the desktop application, not in the phone app.
- The AI app is yours. Omniris controls what a connection can see and do. What your AI app does with an answer, and where it sends it, is governed by that app and its provider.
- AI can be wrong. The measurements come from your surveys, but the AI app writes the sentences around them. Check important figures against the imagery and records.
- The comparison is dated. It describes what Esri had announced and documented in November 2026. Products change.
Where it helps
The weekly site report
"Write this week's report for the north yard." The AI app pulls the changes, volumes and open findings from Omniris and writes it next to the schedule and the notes it already has.
Before the site meeting
"What is still open on the substation, and what changed since we last met?" Findings and changed areas, with the pictures, in two minutes.
Working through findings
Go down the list with the AI app, confirm the real ones, dismiss the false ones, leave a note for the crew. Every change is in the History under the connection's name.
Stockpiles and earthworks
"How much moved this month?" The volume on each survey, the difference, and the map of where.
Asking for the next flight
"That slope needs flying again." A draft request with the area outlined is waiting under Jobs.
Scheduled reports
A script with a Read token checks each site every Monday and posts what changed to the team.
Sites on your own ground
An AI app on your own computer, talking to your own Omniris server, on your own network.
Related papers
- Answers from your own data: Orion, the assistant inside Omniris, which uses the same tools.
- Findings: the located work items a connection can read and update.
- Site Manager and Site Navigator: sites, dated flights and the site change watch.
- Maps you can measure: the maps and 3D surveys the measurements read.
- Temperatures you can measure: thermal flights and temperature maps.
- Evidence you can prove: the custody record downloads and changes are written into.
- Security, encryption and data control: protected files and who can open them.
- Sharing, delivery and integrations: the other ways Omniris connects to the systems you use.
Glossary
- AI app
- An assistant such as Claude, Microsoft Copilot or Cursor that can use outside tools on your behalf.
- AI connection
- A standing permission for one AI app or script to use Omniris as one person.
- Activity
- The list of tool calls a connection has made.
- Change trace
- The areas where a site changed between two flights, each outlined, numbered and measured.
- Consent page
- The Omniris page where you approve a connection and choose what it may do.
- Custody record
- The tamper-evident history Omniris keeps of what happened to each file.
- Draft
- A job request that has been prepared and not submitted. Nothing is sent or charged.
- Finding
- A located work item on a site, with a status, a severity and a history.
- Model Context Protocol (MCP)
- The open standard AI apps use to reach other systems and their tools.
- Personal token
- A secret you make in Omniris and give to a script so it can connect as you.
- Protected file
- A file encrypted in Omniris so that only people you allow can open it.
- Read / Read and change
- The two levels of access a connection can have.
- Tool
- One thing a connection can do, such as measuring a volume or listing findings.
Sources
Esri's own pages and blog posts, read in November 2026.
- Esri Developer, "ArcGIS agentic developer toolkit". developers.arcgis.com
- Esri Developer, "MCP for ArcGIS Location Services (beta)", overview and "Get started". developers.arcgis.com
- Esri Developer, "MCP for ArcGIS Location Services (beta)", "Tools". developers.arcgis.com
- Esri Developer, "MCP for ArcGIS Location Services (beta)", "FAQ". developers.arcgis.com
- Esri Early Adopter Community, "MCP in ArcGIS". earlyadopter.esri.com
- A. Walker, "New MCP Support (beta) and ArcGIS Static Maps Service in Latest ArcGIS Location Platform Release", ArcGIS Blog, June 29, 2026. esri.com
- E. Ole, "Developer's Lounge: Exposing Location Services to Model Context Protocol (MCP) Clients", an interview with L. Smallwood, ArcGIS Blog, July 8, 2026. esri.com