Inspect
Liongard agents reach UniFi controllers and Syncro’s API on a schedule.
Decision brief · Accurate Tech Service
Liongard can turn UniFi configuration drift into Syncro tickets and give an AI analyst grounded access to the resulting history. The upside is real; so are two deal-breakers that only a live pilot can settle.
Liongard becomes the configuration-history layer. Syncro remains where the two-person team works. UniFi stays the place where changes are actually made.
Liongard agents reach UniFi controllers and Syncro’s API on a schedule.
Each run stores a dataprint: inventory, config, posture, and changes over time.
Rules surface drift such as an open SSID, stale firmware, or a new admin.
Actionable Alerts open Syncro tickets; ticket status syncs back to Liongard.
MCP queries, health checks, QBRs, and compliance reports use the stored evidence.
Sources: Liongard Syncro Inspector docs · Syncro ticketing docs · official MCP overview
The official server is hosted by the Liongard tenant. There is no separate server for ATS to deploy or maintain.
POST is the primary streamable HTTP JSON-RPC route. Tokens come from AI Preferences → Access Tokens and are sent as Bearer accessKeyId:accessKeySecret.
Credentials can be scoped to specific environments. Creating them requires the Manage AI permission. OAuth remains experimental; Bearer tokens are the stable path.
Environments, agents, alerts, detections, reconciled devices/identities/domains, metrics, cyber-risk rollups, timelines, reports, and grounded Q&A.
Sources: authentication · tool catalog · official skills · recipe library
The native UniFi inspector covers the operational configuration ATS cares about. Its authentication and network-path requirements are the pilot’s first gate.
Source: official Ubiquiti UniFi inspector docs (docs updated 2025-10-17) · official UniFi analysis recipe
The integration is native and actively documented. Data flows into Liongard for analysis; actionable alerts flow back as tickets.
Sources: Syncro Inspector docs (updated 2025-09-21) · Send tickets to Syncro
Syncro already owns endpoint inventory, assets, tickets, and scripting. Liongard’s differentiated value is cross-vendor state, change history, compliance evidence, and AI analysis.
Uses third-party listings of $29–$33 per environment/month for Core and $39 for Complete. One-year term, billed monthly. Sub-15 pricing and minimum commitments were not verified; sales may quote differently.
Zero added platform cost; lacks automated cross-vendor config history.
Documentation and relationships; needs data fed in.
Network discovery, topology, SNMP, remote access; no Liongard-style SaaS/compliance/MCP layer.
Cross-vendor configuration state, history, detections, reports, and AI querying.
Pricing sources: TrustRadius · GetApp · Domotz pricing · Hudu listing
Do not expand beyond the first 2–3 clients until both controller reachability and ticket quality pass.
Select 2–3 representative sites. Confirm a direct controller endpoint, deploy a self-managed agent where required, and create a local Viewer account with Local Access Only and no MFA.
Create the API key, import and map pilot customers, activate parent/child inspectors, then configure New, Re-Opened, and Closed – Complete mappings with a conservative Issue Type.
Create a pilot-scoped Access Token, run doctor, environment health, and the UniFi recipe. Enable one alert-to-ticket rule and measure signal versus noise before broadening.
Downloads a plain-text list of the technical and commercial questions ATS needs answered.
These items were not verifiable from public sources and need a direct, written answer or tenant test.
Public listings cite “at 15+ environments,” but the minimum and sub-15 pricing were not verified. Ask for the exact 10-, 12-, and 15-environment quote, term, and any onboarding fee.
No free trial was listed; demo/POC language exists. Ask whether ATS can test 2–3 live environments before committing to the annual term.
Have Liongard document the supported controller URL and agent placement for ATS’s actual deployment pattern. Cloud portal access alone is explicitly unsupported.
Community reports mention “Resource not found” for some count/list endpoints. Run the official doctor and a representative tool inventory during the pilot.
Public docs identify the API account/key workflow but did not establish the least-privilege permission set. Get the required scopes in writing.
Choose one outcome—QBR preparation, compliance evidence, or a packaged network-documentation service—and measure whether saved time or new revenue exceeds the platform cost.