The AI Gateway is a single, consistent way for ActiveManage and your application to send a request to a large language model and get an answer back. Which vendor actually answers is configuration, not code, so you can change provider without anything being rebuilt.
Supported providers
Anthropic, OpenAI, Google Gemini, GitHub Models, xAI and Amazon Bedrock. Images can be sent alongside a request where the chosen model accepts them, which is what makes reading a document or a screenshot possible without a separate integration.
Where it is configured
API keys are held in a configuration file on the server rather than in the Architect Panel. That is deliberate — they are credentials with real spending attached, and they belong with your other server-side secrets. Whoever administers your installation will need to set them.
It stores nothing
The gateway keeps no record of what was asked or answered. If you want a log — and there are good reasons to want one — that has to be built into whatever calls it. Decide this early: a model that produces something inappropriate is much easier to investigate if you kept the request.
If it is not configured
With no keys set, every request returns a plain "not configured" message rather than failing. An application offering an optional AI feature therefore degrades to not offering it — worth confirming your application handles that properly, because the message is returned as ordinary text and an application that does not check could display it to a customer as though it were an answer.
Worked Examples
- Support desk: draft a suggested reply for an agent to review and edit.
- Data cleansing: classify free-text enquiries into categories for routing.
- Content: generate a first-draft description that a person then approves.