How the Gargoyle integration with Skydio will work.

What will the integration do?

When a Gargoyle sensor reports a Remote ID detection, Sentinel will be able to send that event into Skydio Cloud as a map marker in DFR Command. Operators can see the detection on the map they already use.

If the agency has enabled auto-launch and the detection meets the rules set in Sentinel, Gargoyle will request that a docked Skydio drone launch to the detected location. The flight remains a Skydio operation. The agency’s operators keep oversight and must be able to abort the flight under their policy and applicable FAA rules.

Gargoyle’s Remote ID sensing is available now and passively receives cooperative Remote ID broadcasts over Wi-Fi and Bluetooth. It cannot detect aircraft that do not broadcast Remote ID. RF and acoustic sensing are coming soon and are not part of this integration as described here.

A detection does not establish intent, identify a payload, or prove that an operation is unauthorized. Review the Remote ID detection guide when setting expectations.

What is the current status?

Coming soon / in development with Skydio. There is no live connector today. Agencies cannot yet connect a Sentinel workspace to Skydio Cloud through this integration. We will update this page when setup is available.

What will you need?

• A Gargoyle sensor deployment and a Sentinel workspace.
• A Skydio Cloud account. Map markers in the DFR workflow and auto-launch assume access to Skydio DFR Command.
• A Skydio Dock and an online docked vehicle, if you want auto-launch.
• A Skydio organization administrator who can create an API token.

How will setup work?

Once the connector is released, setup is planned at a high level as follows:

1. Create an API token in Skydio Cloud. An organization administrator generates a token and grants the scopes listed below.
2. Enter the token in Sentinel. The agency stores the token in its Sentinel configuration so Gargoyle can call the Skydio API on that organization’s behalf.
3. Choose the dock, vehicle, and mission. The team selects the docked aircraft and the mission template Skydio should run when a launch is requested.
4. Set detection rules. In Sentinel, the team defines which detections create a marker and which can also request a launch—for example, activity inside an agreed zone or outside known operations.
5. Monitor and abort as you do today. Operators watch the Skydio console, retain the ability to abort, and follow the agency’s flight program and FAA requirements.

Exact screens and field names will be documented here when the connector is released. The first version does not require Skydio to send webhooks to Gargoyle. Flight-status updates can be considered later if they are needed to confirm a launch.

Which API access will Gargoyle request?

The planned design uses Skydio’s documented Cloud API. The scopes we expect to request are:

• Markers, read and write — to create, update, and remove detection markers on the Skydio map.
• Vehicles, read — to confirm which aircraft are in the organization and whether a vehicle is online.
• Dock, read — to identify the dock associated with an auto-launch.
• Missions, read — to list mission templates so the agency can choose which mission auto-launch should use.
• Mission Schedule, write — to request that a mission run now on an online vehicle.

These names follow Skydio’s public API documentation. The exact set may be confirmed or adjusted with Skydio before release, and this page will be updated to match the final token configuration.

What data will be shared?

For a detection event, Gargoyle plans to send the information needed to place a marker and, when rules allow, to request a launch. That includes the event time, the detected position (latitude and longitude), a short title and description, and any Remote ID broadcast details that were available for that detection—for example, identity or operator location when the broadcast includes them. For auto-launch, Sentinel will also use the mission template and vehicle or dock identifiers the agency has selected.

Gargoyle does not jam, spoof, take down, or take control of aircraft. The Skydio API token grants access only to the scopes the administrator approves.

Who is responsible for the flight?

Auto-launch is a request from Sentinel to Skydio Cloud. It does not transfer responsibility for the flight to Gargoyle. The agency remains responsible for its UAS program, including operator oversight, the ability to abort, and compliance with applicable FAA rules and any waivers or authorizations it holds.

How do I ask a question or get updates?

Use the site assessment form on the contact page. Tell us you are interested in the Skydio integration, and we will follow up as the connector moves from development to setup.