Request a vendor

Short answer: send the request through the vendor request form. Tell us the vendor and product, how many techs would use it, and the questions you would ask the AI about it.

What to include

• Vendor and product name, and whether you are on the vendor's cloud or a self-hosted version.
• The everyday questions your techs would ask, for example "is this machine online and patched?" or "did last night's backup run?".
• Whether the vendor offers API keys or an API user that can be limited to read-only access.
• Whether you would test an early version.

How vendors are chosen

1. How many MSPs use it.
2. How often a tech would ask the AI about it on a normal day.
3. Whether it has a clean, read-only API with admin-managed credentials.
4. Requests from MSPs on StackTether.

What is planned

Next up: ConnectWise PSA, HaloPSA, NinjaOne and Datto RMM. Planned categories after that include Microsoft 365 and Entra ID, documentation (IT Glue, Hudu), security (for example Huntress, SentinelOne), backup (for example Datto BCDR, Axcient), and more. See Supported vendors.

How a new vendor is built

• StackTether builds its own read-only tools on the vendor's API, with the same vendor-neutral names across vendors, rather than passing your AI straight through to a vendor's own tools.
• Every field shown follows a data policy: passwords, license keys, prices and personal identifiers are never shown.
• Each vendor is checked against its live API with a read-only user before it opens.

FAQ

Can you add write actions, such as creating tickets?

Not yet. Every tool is read-only today. See Read and write access (future).