> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engini.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Engini terminology.

| Term | Meaning |
| - | - |
| Application | An integrable product in the Engini catalog, identified by a slug (e.g. `monday`). |
| Connection | An authenticated link between your account and an application (integer id). Tools run through a connection. |
| Auth provider | Your account's own credentials - typically your own OAuth app - for one OAuth2 authentication method of one application, filled once and used by every connection signed in through it. See [Auth providers](/developers/get-started/auth-providers). |
| `kind` | Which sort of connection an application takes: `Regular`, `Key`, or `MCPClient`. Present on connection and application responses; filter with `?kind=`. `OPA` appears on an agent's own responses but is not a valid filter - agents live at `/v1/on-prem-agents`. |
| On-prem agent (OPA) | The Engini component a customer installs behind their firewall to reach SQL Server, Oracle, Priority ERP, and file shares. It polls Engini for work; Engini never connects to it. Managed via `/v1/on-prem-agents`, `client.opa`, and `engini opa`. |
| Key | A connection that holds a credential (API key) rather than a sign-in grant - `kind: "Key"`, and what the web UI's "Keys" tab shows. See [Keys vs Integrations](/developers/get-started/platform-model#keys-vs-integrations). |
| Default connection | The per-application connection used when a tool call doesn't specify one. |
| Tool | One executable action exposed by an application, identified by a slug (e.g. `monday_create_item`). |
| Toolset | A named bundle of connections + permitted tools (GUID id), typically handed to an LLM agent as its tool belt. |
| Trigger | An entity that fires when something changes in a connected app and delivers an event to an endpoint you own. A **trigger type** is the catalog entry (a slug); a **trigger instance** is your configured copy of it (a `ti_…` id), created disabled. Not a workflow step. See [Triggers](/developers/get-started/triggers). |
| Destination | A named HTTPS endpoint a trigger's events are POSTed to, signed with an `esec_…` secret that is shown exactly once. An account has a default; an instance can override it. |
| Object selection | For applications that expose selectable objects (e.g. database tables): choosing which ones the connection syncs. |
| Authentication method | A way to connect to an application (API key, OAuth2, credentials...), each with its own `authenticationId` and field list. |
| `isSuccess` | The field on a tool-execute response that tells you whether the tool actually succeeded - a `200` alone does not. |
| Result handle | A CLI reference (`h42`) to a large tool result stored locally - drill in with `engini tools result`. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.